You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
KubeArmor supports using AppArmor as an enforcer for protecting Kubernetes pods and nodes.
For pods/pod templates, this is done by adding the annotation container.apparmor.security.beta.kubernetes.io/<container_name>: <profile_ref> till now.
However, AppArmor support is moving to GA 🥳 in the upcoming Kubernetes v1.30 release and the annotation would be soon removed in accordance to K8s' deprecation policy.
Describe the solution you'd like
Once K8s 1.30 is released, support both the new AppArmorProfile field that's being added at pod and container level securityContext, along with the old annotation based mechanism for backward compatibility.
Feature Request
Description
KubeArmor supports using AppArmor as an enforcer for protecting Kubernetes pods and nodes.
For pods/pod templates, this is done by adding the annotation
container.apparmor.security.beta.kubernetes.io/<container_name>: <profile_ref>
till now.However, AppArmor support is moving to GA 🥳 in the upcoming Kubernetes v1.30 release and the annotation would be soon removed in accordance to K8s' deprecation policy.
Describe the solution you'd like
Once K8s 1.30 is released, support both the new
AppArmorProfile
field that's being added at pod and container levelsecurityContext
, along with the old annotation based mechanism for backward compatibility.References
The text was updated successfully, but these errors were encountered: