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
Currently, the securityContext can only be defined for the nxrm-app container here
In our enterprise environment, security policies have been enforced and the Helm deployment fails because the sidecar log containers don't comply with those policies.
Can a securityContext be also defined at pod level?
Edit:
I have set readOnlyRootFilesystem & allowPrivilegeEscalation at pod level in a modified Helm chart, but the property did not seem to be inherited by the "log" containers (MS Defender would still complain about it).
Therefore, we would also need to be able to define a securityContext for the "log" containers.
The text was updated successfully, but these errors were encountered:
extravio
changed the title
securityContext as pod level
securityContext as pod level + securityContext for log containers
Apr 4, 2024
Currently, the securityContext can only be defined for the nxrm-app container here
In our enterprise environment, security policies have been enforced and the Helm deployment fails because the sidecar log containers don't comply with those policies.
Can a securityContext be also defined at pod level?
It is also related to this issue: #36
Edit:
I have set readOnlyRootFilesystem & allowPrivilegeEscalation at pod level in a modified Helm chart, but the property did not seem to be inherited by the "log" containers (MS Defender would still complain about it).
Therefore, we would also need to be able to define a securityContext for the "log" containers.
The text was updated successfully, but these errors were encountered: