HoustonPutman commented on issue #594: URL: https://github.com/apache/solr-operator/issues/594#issuecomment-1658526637
Are your pods starting and failing the `liveness`/`readiness` checks, or are they not being created? If its the former, then the issue is likely your `probesRequireAuth: false` option. Have you setup your security.json so that it actually does not require the liveness and readiness endpoint `admin/info/system` to have auth? If there's an error there, the probes will fail. If its the latter, then it's an issue with your secret. (I think this is the case). You are using the same secret (`securityjson`) for both your `bootstrapSecurityJson` secret and your `basicAuthSecret` secret. This is an issue, because the `basicAuthSecret` needs to be a [Basic Authentication Secret](https://kubernetes.io/docs/concepts/configuration/secret/#basic-authentication-secret) which only accepts a username and password. The `bootstrapSecurityJson` secret is supposed to have the `security.json` field, which requires it to be a [Generic Secret](https://kubernetes.io/docs/concepts/configuration/secret/#opaque-secrets). In short, these need to be two separate secrets. You can find more information in the documentation: https://apache.github.io/solr-operator/docs/solr-cloud/solr-cloud-crd.html#custom-securityjson-secret -- 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-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
