[GitHub] [couchdb-helm] kocolosk commented on issue #53: RFC: Is this project still maintained? Fork needed?

[GitBox <gi...@apache.org>]

kocolosk commented on issue #53:
URL: https://github.com/apache/couchdb-helm/issues/53#issuecomment-882782254


   Hi, a couple of comments on the specific issues you mentioned:
   
   - CouchDB 3.1 was added in #36 but we inadvertently merged it into the wrong branch in the `master` -> `main` cutover. That's an oversight, anyone would be welcome to submit a PR to get it merged to the correct branch (and bump to 3.1.1). It's nothing subtle, just bumping default versions and running the YAML generation machinery. The chart itself "just works" with 3.x.
   - "Cluster Setup" is a good discussion topic, some of the work that it does is redundant because the chart knows how to join nodes into a cluster automatically using the `seedlist` functionality. My general thought is that if there are k8s-centric ways to implement the things that "cluster setup" does then we should consider them.
   
   I'd also point out that a lot of the energy for automating the management of CouchDB in Kubernetes is being directed to the [CouchDB Operator](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-apache-couchdb-overview#apache-couchdb-operator-overview). If you haven't seen that, maybe check to see if the extra functionality it provides is a good fit. I know the IBM folks provide commercial support for it as well if needed.
   
   Echoing what Bob said, if you're inclined to spend some cycles on the Helm chart, there shouldn't be any need to fork it. We'd be happy to have the extra input on this project!


-- 
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: notifications-unsubscribe@couchdb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org