Closed jmesnil closed 1 year ago
Kubernetes Pod Security Standards are being updated (as explained in https://sdk.operatorframework.io/docs/best-practices/pod-security-standards/) and the WildFly Operator lags behind these changes.
In the mainbranch, the user can specify the SecurityContext on the deployed Pod templates to control the behaviour (#238).
main
SecurityContext
However, it is missing a seccompProfile to comply with the security standards.
seccompProfile
In addition, we can provide a good default value for this security context and do not need to ask the user to specify it.
Kubernetes Pod Security Standards are being updated (as explained in https://sdk.operatorframework.io/docs/best-practices/pod-security-standards/) and the WildFly Operator lags behind these changes.
In the
mainbranch, the user can specify theSecurityContexton the deployed Pod templates to control the behaviour (#238).However, it is missing a
seccompProfileto comply with the security standards.In addition, we can provide a good default value for this security context and do not need to ask the user to specify it.