Couchbase operator 2.0 and volumeClaimTemplates for CB 6.5

Couchbase Server Kubernetes
1

@tommie or @simon.murray
I am using below custom config for Helm Chart for operator . Can you please point issues there as I am not seeing volumemounts happening inside the POD for Operators . Is that normal for operator and
volumemounts can’t be attached ? and volumeClaimTemplates can’t be defined ?

vscode
vscode607×774 26.8 KB

2

I’m having the same issue with volumes on the cluster: values. It shows up in dry-run but is ignored

cluster:
  servers:
    default:
      size: 1
      services:
        - data
        - index
        - query
        - search
        - eventing
  volumeMounts:
    default: couchbase
    data: couchbase
    logs: couchbase
    index: couchbase
volumeClaimTemplates:
  - metadata:
      name: couchbase
    spec:
      storageClassName: "standard"
      resources:
        requests:
          storage: 1Gi
3

Hi @jmallory @eldorado
The indentation needs to be updated here as documented volumeMounts are per-config and claimTemplates are per-cluster, ie:

cluster:
  servers:
    default:
      size: 1
      services:
        - data
        - index
        - query
        - search
        - eventing
      volumeMounts:
        default: couchbase
        data: couchbase
        index: couchbase
  volumeClaimTemplates:
    - metadata:
        name: couchbase
      spec:
        storageClassName: "standard"
        resources:
          requests:
            storage: 1Gi

https://docs.couchbase.com/operator/current/helm-couchbase-config.html

Also @jmallory logs cannot share persisted in same group with other persistent services.
https://docs.couchbase.com/operator/current/reference-couchbasecluster.html#spec-servers-volumemounts-default

4

So locally, I have the correct indentation but it looks like this is more complicated when running locally on dev laptop.