PodSecurityPolicy is removed in 1.25

Bug #1986856 reported by Adam Dyess
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Fix Released
Critical
Stone Preston
Adam Dyess (addyess)
Changed in charm-kubernetes-master:
importance: Undecided → Critical
milestone: none → 1.25
Revision history for this message
George Kraft (cynerva) wrote :
Changed in charm-kubernetes-master:
status: New → Fix Committed
assignee: nobody → Stone Preston (stonepreston)
Revision history for this message
Stone Preston (stonepreston) wrote :

An issue was discovered with the previous fix, and it was fixed in https://github.com/charmed-kubernetes/charm-kubernetes-control-plane/pull/241

summary: - PodSecurityPolicy is deprecated in 1.25
+ PodSecurityPolicy is removed in 1.25
Adam Dyess (addyess)
Changed in charm-kubernetes-master:
status: Fix Committed → Fix Released
Revision history for this message
Ebrar Leblebici (birru2) wrote :

It seems we still have pod-security-policy config option. I deployed CK with kubernetes-control-plane in version 1.28.8 (rev 321) and still seeing this config option:

$ juju config kubernetes-control-plane | grep pod-security-policy
  pod-security-policy:
      [0] https://kubernetes.io/docs/concepts/policy/pod-security-policy/

Revision history for this message
Adam Dyess (addyess) wrote :

The config is still there. But it's inactive if the underlying cluster is running 1.25 and beyond.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.