guillaumBrisard opened a new issue, #587: URL: https://github.com/apache/solr-operator/issues/587
I would like everything to be set and ready to use for my client without any additionnal configuration through my pipeline. Right now I use API for 1. uploading configset 2. creating collections 3. creating aliases 4. ... It's superset of these enhancements https://github.com/apache/solr-operator/issues/85 https://github.com/apache/solr-operator/issues/59 or this SIP https://cwiki.apache.org/confluence/display/SOLR/SIP-18%3A+A+Solr+Kubernetes+Module+for+native+integration It seems that we can't use `lifecycle.podstrart` because the cluster is not ready yet https://kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/#discussion _Kubernetes sends the postStart event immediately after the Container is created. There is no guarantee, however, that the postStart handler is called before the Container's entrypoint is called._ In waiting this, what is the best practices to do it, right now with 9.2 ? -- 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]
