janhoy commented on issue #109: URL: https://github.com/apache/solr-operator/issues/109#issuecomment-6477168162
Closing as declined. The custom `PodOptions` type is a deliberate choice: the SolrCloud CRD abstracts the underlying Kubernetes resources so that Solr can be run on Kubernetes without full knowledge of PodSpec, and the operator needs to own parts of the pod spec (probes, env, lifecycle hooks, volumes) that a user-supplied PodSpec would conflict with. The direction taken instead has been to add targeted passthrough fields to `customSolrKubeOptions.podOptions` as needs arise, which has covered most of what an embedded PodSpec would have. If a specific field is missing, a small issue asking for that field is the fastest route. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
