Skip to content

helm: add deployment securityContext values #6136

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.

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

Merged
merged 2 commits into from
Feb 9, 2023
Merged

Conversation

ericpaulsen
Copy link
Member

@ericpaulsen ericpaulsen commented Feb 9, 2023

this PR adds support for configuring the Coder deployment's securityContext (for both pod & container) in the values file. this comes in handy when deploying Coder on OpenShift, which applies SecurityContextConstraints to deployments.

one question i have - since the Coder deployment consists of a single container, is it necessary for us to have a pod-level securityContext? the securityContext set at the container-level takes precedence over the pod-level context.

keeping the podSecurityContext values is beneficial if there is any possibility of us adding containers to the deployment. otherwise, I don't see much a reason to keep it.

@ericpaulsen ericpaulsen merged commit 22f6400 into main Feb 9, 2023
@ericpaulsen ericpaulsen deleted the securitycontexts branch February 9, 2023 18:26
@github-actions github-actions bot locked and limited conversation to collaborators Feb 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants