Deployment securityContext part is missing on creation

[sebastien-helbert]

Setup

• Rancher version: 2.6.2
• Browser type & version: Google Chrome

Describe the bug
securityContext section is missing when created from new UI which prevents pods from starting when Pod Security Policy Support is enabled.

To Reproduce
Create a new workload of type Deployment from UI

Result

Expected Result

Add this section in yaml file like the old UI does :

        securityContext:
          allowPrivilegeEscalation: false
          capabilities: {}
          privileged: false
          readOnlyRootFilesystem: false
          runAsNonRoot: false

It may be somewhat related to #4238

[catherineluse]

Should this be in the v2.6.4 release notes under known issues?

[gaktive]

@jtravee we'll need a known issue in 2.6.4 for this.

[jtravee]

@jtravee we'll need a known issue in 2.6.4 for this.

Got it, ty!

[xhejtman]

Hello,

if CIS profile is in use, it would be really good, if default security context could be pre-set so that it meets CIS requirements. With PSA it means setting capablity drop, allowprivilegesescalation, seccompprofile. Without this, it is not possible to run pod from UI without editing yaml manifest.