apache / apache/couchdb-helm

Figure out a way to avoid manual action after deploying a cluster with the helm chart

Open
#92 2 comments 1 reaction 0 assignees View on GitHub
Dominant language
Mustache
Stars
55
Forks
68
PR merge metrics
No merged PRs in 30d

Description

**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:

```
Once all of the Pods are fully Ready, execute the following command to create
some required system databases
```

**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. an `upgrade`.

https://github.com/apache/couchdb-helm/blob/78eff8c0fc3d8524f1a5c0c27880eaf2df98a2f4/couchdb/templates/NOTES.txt#L5-L8

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.