-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Figure out a way to avoid manual action after deploying a cluster with the helm chart #92
Comments
Just a bit more digging on this. At a minimum, this request seems to create the It is also not idempotent: First response:
Second:
|
Hi @colearendt, I contributed with automation of placement couchdb nodes across availability zones in the cluster. You can use the Please use the tag 0.3.0 in I understand that you may not want to automate the placement of nodes across availability zones, but it's useful if you're using a cluster in a cloud environment like AWS and you want to configure HA, for example. |
Is your feature request related to a problem? Please describe.
After deploying the helm chart, there is a very helpful / explanatory message in
NOTES.txt
about cluster state:Describe the solution you'd like
It would be nice if this manual command did not need to be run. What is it for? Is there a way to deploy a one-shot job or something alongside that will do this bootstrapping for us? What are the downsides if you run this command multiple times?
At a minimum, the quoting on the command was a little off which made it tricky to use
Describe alternatives you've considered
Additional context
It also surprises me that this is printed every time. I suspect there are values in helm that we could use to determine whether this is necessary to print. For instance, I'm pretty sure you can tell when you have an
install
vs. anupgrade
.couchdb-helm/couchdb/templates/NOTES.txt
Lines 5 to 8 in 78eff8c
The text was updated successfully, but these errors were encountered: