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

Apache CouchDB Helm Chart

Results 51 couchdb-helm issues
Sort by recently updated
recently updated
newest added

### **Describe the bug** Upon executing helm install couchdb -n couchdb couchdb/couchdb -f values.yaml, the main container enters a continuous restart loop, lacking explanatory logs. This issue surfaces when persistence...

**Describe the bug** I am getting CrashLoopBackoff of a CouchDB pod, when I am deploying it with persistenVolume. values for Helm Chart ``` clusterSize: '1' persistentVolume: enabled: 'true' storageClass: 'efs-sc-couchdb'...

Update chart-testing and kind to the current versions. #### What this PR does / why we need it: Update test dependencies to stay current with chart-testing and KinD. This does...

A default install of the helm chart, like so: ```bash helm install couchdb couchdb/couchdb \ --namespace $namespace \ --set couchdbConfig.couchdb.uuid=1edba19879809c3ae67e2abec4054579 \ --set persistentVolume.enabled=true ``` will simply not work. It may...

**Describe the bug** On existing couchdb clusters a upgrade from version 3.6.0 to 3.6.1 with default erlang cookie will fail. **A clear and concise description of what the bug is.**...

#### What this PR does / why we need it: We utilize Helm's `lookup` command to store a generated `uuid` in an "internal" secret in Kubernetes. This allows generating the...

I wonder what stance is on **idempotency** of the CouchDB Helm chart install action? It seems to be a debated issue in the Helm world, but one which the CouchDB...

**Describe the bug** From Helm v3 the chart installation is: `helm install [NAME] [CHART] [flags]` Therefore there is need to update the installation commands in the [guide](https://github.com/apache/couchdb-helm/blob/main/couchdb/README.md) to this new...

**Describe the bug** unable to setup couch db on ipv6 only environemnt **Version of Helm and Kubernetes**: CouchDB - 3.3.4 Kubernetes: 1.22 **What happened**: After installing the chart the pods...

**Describe the bug** After restarting a pod, the node fails to join the cluster properly, and we're getting an error on Fauxton, that displays 'this database failed to load' on...