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.

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

Improvement: Ability to set SecurityContext #7282

Open
OS-marcelopereira opened this issue Feb 3, 2023 · 4 comments
Open

Improvement: Ability to set SecurityContext #7282

OS-marcelopereira opened this issue Feb 3, 2023 · 4 comments

Comments

@OS-marcelopereira
Copy link

OS-marcelopereira commented Feb 3, 2023

Improvement: Ability to set SecurityContext

Expected Behavior

I have a usecase where I need to set a SecurityContext block on the APIServer deployment, the apiserver container and componentResources, in order to comply with security requitements.

Looking at the documentation, I see that such a thing is not available for the APIServerDeploymentContainer, APIServerDeploymentContainer and APIServerDeploymentContainer

Is this something that might be possible in the future?

Calico version: v3.24.5

@caseydavenport
Copy link
Member

Yep, looks like we hard-code a security context here: https://github.com/tigera/operator/blob/master/pkg/render/apiserver.go#L940

It should be possible to expose an option for this, although we need to be careful not to expose an option that can easily break user's clusters.

@clayvan
Copy link

clayvan commented Nov 20, 2023

tigera/operator#2720

@flo-mic
Copy link

flo-mic commented Feb 29, 2024

is there any update on this?

@caseydavenport
Copy link
Member

Just waiting on someone to pick up the torch for this one - I think it's generally agreed to be a good thing. Any takers?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants