PodSecurityPolicy does not work correctly with kube-controller-manager connecting via insecure port
Bug #1841965 reported by
George Kraft
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes Control Plane Charm |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
From https:/
> At this moment controller managers services are talking to API server on the insecured port. (i.e:: auth and authz bypassed) PodSecurityPolicy need controller-manager service running, authentificated with it's own credential. Otherwise all PodSecurityPolicy objects would be allowed for each Pod created by controller-manager (ReplicaSet, Deployment...)
Revision history for this message
| George Kraft (cynerva) wrote | #1 |
| Changed in charm-kubernetes-master: | |
| status: | New → Fix Committed |
| milestone: | none → 1.16 |
| Changed in charm-kubernetes-master: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed by https:/
Thanks to pierrop for the contribution!