dan-niles opened a new issue, #679: URL: https://github.com/apache/solr-operator/issues/679
I noticed that the default security.json template is missing the permission for the `/admin/info/system` endpoint, in the [SolrCloud CRD documentation](https://github.com/apache/solr-operator/blob/main/docs/solr-cloud/solr-cloud-crd.md?plain=1#L998). I was trying to deploy Solr with a custom security.json using the `bootstrapSecurityJson` option. I used the security.json template provided in the SolrCloud CRD documentation, but my Solr pods weren't starting. So I used the [other option of having the operator bootstrap a security.json](https://apache.github.io/solr-operator/docs/solr-cloud/solr-cloud-crd.html#option-1-bootstrap-security), and it worked. When I compared the security.json generated by the operator and the template provided in the documentation, the following permission object for the `/admin/info/system` endpoint was missing in the docs. ```json { "name": "k8s-probe-0", "role": null, "collection": null, "path": "/admin/info/system" } ``` Once I included this in my custom security json, my pods were starting up, and Solr was working correctly. -- 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]
