Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Allow configured podSecurityContext to apply to OpenShift as well #952

Closed
amisevsk opened this issue Oct 18, 2022 · 0 comments · Fixed by #953
Closed

Allow configured podSecurityContext to apply to OpenShift as well #952

amisevsk opened this issue Oct 18, 2022 · 0 comments · Fixed by #953
Assignees
@amisevsk
Milestone
v0.17.x

Comments

@amisevsk
Copy link
Collaborator

Description

The DevWorkspace Operator Config .config.workspace.podSecurityContext field is currently ignored on OpenShift (as by default you cannot set e.g. a custom runAsUser). However, other fields in podSecurityContext may be useful, so it would be convenient to be able to configure them on OpenShift.

Additional context
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amisevsk amisevsk

Labels
None yet
Projects
None yet
Milestone
v0.17.x
Development

Successfully merging a pull request may close this issue.

Add container security context field to DevWorkspace Operator Config amisevsk/devworkspace-operator
1 participant
@amisevsk