claudio4j commented on PR #5558: URL: https://github.com/apache/camel-k/pull/5558#issuecomment-2137566433
I could reproduce the error in #4974 by installing camel-k 2.1.0 from operator hub in openshift 4.15.14. Updated to Camel K 2.2.0 from operator hub. Then there is no error anymore. The fix was provided by #4932 The problem was in 2.1.0, the `runAsUser` field of `securityContext` was set from the platform namespace, while the correct one should be from the integration namespace. The proposal of the test is to run an integration in a restricted namespace, whereas the `restricted` policy is the more [secured one by the policy definition](https://kubernetes.io/docs/concepts/security/pod-security-standards/). However when running in openshift the operator correctly sets the `securityContext` in compliance with the `restricted` policy, whereas when running not on openshift profile, the `securityContext` is not applied, so that results in error when the namespace is set with the `restricted` policy. I will open an issue to set the `securityContext` policy regardless if it's running in openshift, this way the integration can correctly run in a restricted policy in any kubernetes cluster. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
