couchdb-helm icon indicating copy to clipboard operation
couchdb-helm copied to clipboard

Cluster setup wizards does not work in microk8s

Open kingledion opened this issue 2 years ago • 0 comments

Describe the bug The cluster setup wizard does not work in microk8s, while it does work in k3s, kind, and minikube.

The setup command is

curl -s http://127.0.0.1:5984/_cluster_setup  -X POST -H "Content-Type: application/json" -d '{"action": "finish_cluster"}' -u admin

executed on one of the nodes within k8s, as per the chart's Note.

Version of Helm and Kubernetes: Helm v3.6.3 Kubernetes v1.21.11 (via microk8s)

What happened:

{"error":"setup_error","reason":"Cluster setup timed out waiting for nodes to connect"}

What you expected to happen: Successful completion of setup wizard, creation of _users and _replication table, etc

How to reproduce it (as minimally and precisely as possible):

Install microk8s sudo snap install microk8s --classic --channel=1.21 (you may need more to get kubectl working)

Activate addons for microk8s; dns and storage are required for this config, traefik and rbac are also installed for replication

microk8s enable dns
microk8s enable storage

Install CouchDB helm chart kubectl create secret generic cluster-couchdb --from-literal=adminUsername=admin --from-literal=adminPassword=dbpass --from-literal=cookieAuthSecret=dbcookiepass --from-literal=erlangCookie=monster helm install my-release couchdb/couchdb --set couchdbConfig.couchdb.uuid=$(curl https://www.uuidgenerator.net/api/version4 2>/dev/null | tr -d -) --version 3.6.1 -f ./values.yaml with values.yaml like:

createAdminSecret: false

persistentVolume:
  enabled: true
  accessModes:
    - ReadWriteOnce
  size: 10Gi
  # storageClass: "-"

I also did this with version=3.3.3 with same issue.

Anything else we need to know: I tried on two machines, both of which were running Ubuntu 20.04. Between the two machines, I verified that this worked with all of minikube, kind and k3s.

kingledion avatar Apr 25 '22 19:04 kingledion