We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When the DWOC defines a containerSecurityContext:
containerSecurityContext
containerSecurityContext: allowPrivilegeEscalation: true capabilities: add: - SETGID - SETUID
the containerSecurityContext is not applied to the workspace containers that are added via routing class.
This behaviour is most easily reproduced with Eclipse Che (which uses the che routing class), see eclipse-che/che#22747.
che
In the case of Eclipse Che, the workspace container that does not have the containerSecurityContext set, is the che-gateway conatiner.
che-gateway
The containerSecurityContext should be applied to all workspace containers
The text was updated successfully, but these errors were encountered:
Fixed by #1358
Sorry, something went wrong.
No branches or pull requests
Description
When the DWOC defines a
containerSecurityContext
:the
containerSecurityContext
is not applied to the workspace containers that are added via routing class.This behaviour is most easily reproduced with Eclipse Che (which uses the
che
routing class), see eclipse-che/che#22747.In the case of Eclipse Che, the workspace container that does not have the
containerSecurityContext
set, is theche-gateway
conatiner.Expected behavior
The
containerSecurityContext
should be applied to all workspace containersAdditional context
The text was updated successfully, but these errors were encountered: