HoustonPutman commented on issue #517: URL: https://github.com/apache/solr-operator/issues/517#issuecomment-1428310490
> The managed zk feature of solr-operator is great. Would be a pity if all users had to manually configure bitnami chart for every new solr cluster, and feed the ZK connection string into solr. Are there ways do do a tighter integration with binami out of the box? I'm not sure this is possible unfortunately. Maybe we could ask for a bitnami chart release name and make some guesses about other stuff, but it seems weird. > I may be lacking some insights here, but @HoustonPutman @janhoy how would it impact if we were to use the [bitnami zookeeper](https://github.com/bitnami/charts/tree/main/bitnami/zookeeper) _(looks much more active)_ chart instead of the `pravega/zookeeper-operator` chart? I don't see any operator there, then maybe the Solr operator needs to take care of the zookeeper-cluster there, which now the zookeeper-operator does. So the bitnami zookeeper chart isn't an operator, it just uses the built in kubernetes resources to implement Zookeeper. The solr operator is never going to "take care" of zookeeper nodes, because its purpose is to run Solr. I've used the bitnami chart and it looks like there is very little need for "operator" functionality for zookeeper clusters, but I could be wrong there. -- 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]
