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
Is your feature request related to a problem? Please describe.
I cannot set the security context for the created containers. It is only allowed to set the security context of the created pods.
Describe the solution you'd like
Please implement security context configuration for the created containers additionally to the security context of the created pods.
Describe alternatives you've considered
Currently there are no alternatives available.
Additional Information
It should be allowed to set the security context for the created containers to prevent privilege escalation and to configure read only root filesystem. Both options are a Kubernetes Security best practice.
The text was updated successfully, but these errors were encountered:
This is a controversial one since adding support for this makes the minimal version of Kubernetes to be 1.22 I believe since that's when Container Security Context was added, with the release of kubernetes 1.26 we are now only supporting down to 1.21 so when 1.22 is our floor we will add support for Container Security Context.
Unless we find a backwards compatible approach to add this, we cannot add it, but we will look into it.
Is your feature request related to a problem? Please describe.
I cannot set the security context for the created containers. It is only allowed to set the security context of the created pods.
Describe the solution you'd like
Please implement security context configuration for the created containers additionally to the security context of the created pods.
Describe alternatives you've considered
Currently there are no alternatives available.
Additional Information
It should be allowed to set the security context for the created containers to prevent privilege escalation and to configure read only root filesystem. Both options are a Kubernetes Security best practice.
The text was updated successfully, but these errors were encountered: