-
Notifications
You must be signed in to change notification settings - Fork 111
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
Add support to set capabilities on Solr cloud container's security context #489
Comments
@HoustonPutman is support for setting capabilities on |
@ollixy you cannot set capabilities on the podSecurityContext, cf. https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#podsecuritycontext-v1-core. What we need is a separate option to specify the securityContext of each container in the pod. @HoustonPutman +1 for this issue, since solr is incompatible when using sokme restricted PSS and enforcing these with keyverno (for example). I'll try to file an PR, but my knowledge about operators is quite limited. |
Sounds good, I'm very happy to help once you get a start 🙂 |
@mmoscher @HoustonPutman any news on this one? |
Any news on this one? |
No news from me. I'm not running openshift, so I don't really know what needs to be done. If someone wants to start a PR, then I'm very happy to help usher it through. |
Hi all! a new version was recently released (April 12, 2024, Apache Solr Operator™ v0.8.1 available, there is no solution to our problem) is there any news on our problem? |
@ollixy , @pareekdevanshu, @mmoscher, @aaronsuns , @AyzekTime |
I'm running into this issue on EKS. @janhoy / @HoustonPutman Are these extra capabilties/privs ever actually needed? If not, we can likely hardcode in the changes made in this comment: Here is an example of a values.yaml I'm trying to use for a Solr Cluster:
|
Hi Team,
Currently It is possible to set capabilities for
initContainers
andsidecarContainers
, Eg:But, there is no way to set capabilities on Solr cloud container's security context, can you please help in adding support for it?
The text was updated successfully, but these errors were encountered: