-
Notifications
You must be signed in to change notification settings - Fork 201
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
SRS add support for setting securityContext #711
Comments
@reddy-srinivas @ravitejamekapega Can you please take a look? |
@konire @kishorv10 @reddy-srinivas @ravitejamekapega, Perhaps this can be looked at more generic. I am facing customisations to the template files due to company security settings and therefore for all containers/pods I need to add the following:
It would be great if these securityContext values can be specified in the Especially on in-company shared k8s platforms, security becomes more and more important. |
@dekke046 Are you asking for SRS subchart or backing services or Pega charts? Can you be specific. |
At least I had to make securityContext changes to the following files for the Pega chart:
For the backingservices: I have not checked the addons charts files yet. I only did helm install, do not yet have any experience with helm upgrade for version upgrade activities, that will probably start a container doing all the database upgrade SQL work and also needs to have the proper securityContext settings. |
@dekke046 Are both the Pegasearch subchart and SRS backing service utilized in your deployment? |
The current ask is partially completed in #750 |
Thank you, we will move towards SRS soon! |
Excellent @kishorv10 , |
Is your feature request related to a problem? Please describe.
The SRS chart currently does not support setting the securityContext on pod or container.
Describe the solution you'd like
I'd like to (optionally) set the securityContext.
Describe alternatives you've considered
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: