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

Container SecurityContext seems not available #241

Open
timsn opened this issue Feb 3, 2022 · 6 comments
Open

Container SecurityContext seems not available #241

timsn opened this issue Feb 3, 2022 · 6 comments
Labels
good first issue Good for newcomers

Comments

@timsn
Copy link

timsn commented Feb 3, 2022

When looking through the FlinkCluster CRD I can see there are securityContext definitions for Jobmanager, Taskmanger and Job specs. All of these are of the type PodSecurityContext which is fine.
Besides that it would great to be able to set the corresponding Container SecurityContext as well. This would allow to set options like allowPrivilegeEscalation, readOnlyRootFilesystem, drop capabilities and others which are not available in the PodSecurityContext. This is important in some cluster environments like ours where we need to fulfill certain security policies.

@regadas
Copy link
Contributor

regadas commented Feb 4, 2022

Hey @timsn! adding that makes total sense! let me know if you want to take a stab at it.

@anythingbyme
Copy link

Hi @regadas I cloned the latest but still do not see the property "readOnlyRootFilesystem". I'm a newbie, so could you please confirm if it is already complete or work needs to be done? If work needs to be done, I can take a stab at it. Please let me know

@regadas
Copy link
Contributor

regadas commented Dec 12, 2022

Hi @anythingbyme, yup this work is still pending.

@acherla
Copy link

acherla commented Jan 16, 2023

Hi @anythingbyme, yup this work is still pending.

Need any assistance on implementing this change? Our teams are also looking for something similar so I implemented the change in our local build of the operator

@regadas
Copy link
Contributor

regadas commented Mar 14, 2023

Hi @acherla would you mind making a PR for this?

@g4ze
Copy link

g4ze commented Jul 3, 2023

is the issue resolved? Can I work on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

5 participants