[bitnami/nginx] deployment fail because of OpenShift restricted-v2 about charts

[antoinetran]

Workaround: set values.yaml like this, and it works

global:
  compatibility:
    openshift:
      adaptSecurityContext: "force"
containerSecurityContext:
  runAsUser: null
  runAsGroup: null

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

[antoinetran]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

Ok, I tried with this pull request :)

[darren-bell-optiva]

Hi. This same problem exists for the nginx-ingress-controller

charts/bitnami/nginx-ingress-controller/templates/controller-deployment.yaml

Line 81 in 43ccdb2

securityContext: {{- omit .Values.containerSecurityContext "enabled" | toYaml | nindent 12 }}

and also the daemonset

[carrodher]

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!

[antoinetran]

Hi. This same problem exists for the nginx-ingress-controller

charts/bitnami/nginx-ingress-controller/templates/controller-deployment.yaml

Line 81 in 43ccdb2

securityContext: {{- omit .Values.containerSecurityContext "enabled" | toYaml | nindent 12 }}

and also the daemonset

I don't mind, I added the fix in my branch too for nginx-ingress-controller.