You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "bcbrockway (via GitHub)" <gi...@apache.org> on 2024/09/23 13:40:34 UTC

Re: [I] Add support to set capabilities on Solr cloud container's security context [solr-operator]

bcbrockway commented on issue #489:
URL: https://github.com/apache/solr-operator/issues/489#issuecomment-2368300581

   To the maintainers: Is there a particular reason you specify your own fields in podOptions.podSecurityContext instead of just accepting a [k8s podSecurityContext API type](https://pkg.go.dev/k8s.io/api/core/v1#PodSecurityContext)? Using the upstream k8s type would mean that no-one would manually have to add fields available in the k8s type to the securityContext objects in this CRD, right? I'm definitely no expert, but I've seen this done in other operators.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org