--- title: CouchbaseCluster Resource pubDate: 2026-08-17T09:53:44.266Z antora: editUrl: https://github.com/couchbase/couchbase-operator/edit/2.7.x/docs/user/modules/ROOT/pages/resource/couchbasecluster.adoc xref: xref:2.7@operator::resource/couchbasecluster.adoc[] --- [Consult the llms.txt file for a full list of contents](/llms.txt) [View original HTML](/operator/2.7/resource/couchbasecluster.html) # CouchbaseCluster Resource The CouchbaseCluster resource represents a Couchbase cluster. It allows configuration of cluster topology, networking, storage and security options. The following is an example resource, depicting the overall structure and any defaults (consult the field reference for valid values for "empty" values, such as empty strings etc.): ```yaml apiVersion: v2 kind: CouchbaseCluster metadata: name: "" spec: antiAffinity: false autoResourceAllocation: cpuLimits: 4 cpuRequests: 2 enabled: false overheadPercent: 25 autoscaleStabilizationPeriod: "" backup: annotations: image: couchbase/operator-backup:1.3.1 imagePullSecrets: - name: "" labels: managed: false nodeSelector: {} objectEndpoint: secret: "" url: "" useVirtualPath: false resources: {} s3Secret: "" selector: {} serviceAccountName: couchbase-backup tolerations: - effect: "" key: "" operator: "" tolerationSeconds: 0 value: "" useIAMRole: false buckets: managed: false selector: matchExpressions: - key: "" operator: "" values: - "" matchLabels: synchronize: false cluster: analyticsServiceMemoryQuota: 1Gi autoCompaction: databaseFragmentationThreshold: percent: 30 size: "" parallelCompaction: false timeWindow: abortCompactionOutsideWindow: false end: "" start: "" tombstonePurgeInterval: 72h viewFragmentationThreshold: percent: 30 size: "" autoFailoverMaxCount: 1 autoFailoverOnDataDiskIssues: false autoFailoverOnDataDiskIssuesTimePeriod: 120s autoFailoverServerGroup: false autoFailoverTimeout: 120s clusterName: "" data: auxIOThreads: 0 minReplicasCount: 0 nonIOThreads: 0 readerThreads: 0 writerThreads: 0 dataServiceMemoryQuota: 256Mi eventingServiceMemoryQuota: 256Mi indexServiceMemoryQuota: 256Mi indexStorageSetting: memory_optimized indexer: enableShardAffinity: false logLevel: info maxRollbackPoints: 2 memorySnapshotInterval: 200ms numReplica: 0 redistributeIndexes: false stableSnapshotInterval: 5s storageMode: memory_optimized threads: 0 query: backfillEnabled: True cboEnabled: True cleanupClientAttemptsEnabled: True cleanupLostAttemptsEnabled: True cleanupWindow: 60s completedLimit: 4000 completedMaxPlanSize: 262144 completedTrackingAllRequests: false completedTrackingEnabled: True completedTrackingThreshold: 7s logLevel: info maxParallelism: 1 memoryQuota: 0 nodeQuotaValPercent: 67 numActiveTransactionRecords: 1024 numCpus: 0 pipelineBatch: 16 pipelineCap: 512 preparedLimit: 16384 scanCap: 512 temporarySpace: 5Gi temporarySpaceUnlimited: false timeout: "" txTimeout: 0ms useReplica: false queryServiceMemoryQuota: "" searchServiceMemoryQuota: 256Mi enableOnlineVolumeExpansion: false enablePreviewScaling: false envImagePrecedence: false hibernate: false hibernationStrategy: "" image: "" logging: audit: disabledEvents: - 0 disabledUsers: - "" enabled: false garbageCollection: sidecar: age: 1h enabled: false image: busybox:1.33.1 interval: 20m resources: {} rotation: interval: 15m pruneAge: 0 size: 20Mi logRetentionCount: 0 logRetentionTime: "" server: configurationName: fluent-bit-config enabled: false manageConfiguration: True sidecar: configurationMountPath: /fluent-bit/config/ image: couchbase/fluent-bit:1.2.1 resources: {} monitoring: prometheus: authorizationSecret: "" enabled: false image: "" refreshRate: 60 resources: {} networking: addressFamily: "" adminConsoleServiceTemplate: {} adminConsoleServiceType: NodePort adminConsoleServices: - "" cloudNativeGateway: image: "" logLevel: info terminationGracePeriodSeconds: 75 tls: serverSecretName: "" disableUIOverHTTP: false disableUIOverHTTPS: false dns: domain: "" exposeAdminConsole: false exposedFeatureServiceTemplate: {} exposedFeatureServiceType: NodePort exposedFeatureTrafficPolicy: "" exposedFeatures: - "" loadBalancerSourceRanges: - "" networkPlatform: "" serviceAnnotations: tls: allowPlainTextCertReload: false cipherSuites: - "" clientCertificatePaths: - delimiter: "" path: "" prefix: "" clientCertificatePolicy: "" nodeToNodeEncryption: "" passphrase: rest: addressFamily: inet headers: timeout: 5000 url: "" verifyPeer: True script: secret: "" rootCAs: - "" secretSource: clientSecretName: "" serverSecretName: "" static: operatorSecret: "" serverSecret: "" tlsMinimumVersion: TLS1.2 waitForAddressReachable: 10m waitForAddressReachableDelay: 2m onlineVolumeExpansionTimeoutInMins: 0 paused: false platform: "" recoveryPolicy: "" rollingUpgrade: maxUpgradable: 0 maxUpgradablePercent: "" security: adminSecret: "" ldap: authenticationEnabled: True authorizationEnabled: false bindDN: "" bindSecret: "" cacert: "" cacheValueLifetime: 30000 encryption: "" groupsQuery: "" hosts: - "" middleboxCompMode: True nestedGroupsEnabled: false nestedGroupsMaxDepth: 10 port: 389 serverCertValidation: false tlsSecret: "" userDNMapping: query: "" template: "" podSecurityContext: fsGroup: 0 fsGroupChangePolicy: "" runAsGroup: 0 runAsNonRoot: false runAsUser: 0 seLinuxOptions: level: "" role: "" type: "" user: "" seccompProfile: localhostProfile: "" type: "" supplementalGroups: - 0 sysctls: - name: "" value: "" windowsOptions: gmsaCredentialSpec: "" gmsaCredentialSpecName: "" hostProcess: false runAsUserName: "" rbac: managed: false selector: {} securityContext: allowPrivilegeEscalation: false capabilities: add: - "" drop: - "" privileged: false procMount: "" readOnlyRootFilesystem: false runAsGroup: 0 runAsNonRoot: false runAsUser: 0 seLinuxOptions: level: "" role: "" type: "" user: "" seccompProfile: localhostProfile: "" type: "" windowsOptions: gmsaCredentialSpec: "" gmsaCredentialSpecName: "" hostProcess: false runAsUserName: "" uiSessionTimeout: 0 securityContext: {} serverGroups: - "" servers: - autoscaleEnabled: false env: [] envFrom: [] image: "" name: "" pod: {} resources: {} serverGroups: - "" services: - "" size: 0 volumeMounts: analytics: - "" data: "" default: "" index: "" logs: "" softwareUpdateNotifications: false upgradeProcess: "" upgradeStrategy: "" volumeClaimTemplates: [] xdcr: managed: false remoteClusters: - authenticationSecret: "" hostname: "" name: "" replications: selector: {} tls: secret: "" uuid: "" status: allocations: - allocatedMemory: "" allocatedMemoryPercent: 0 analyticsServiceAllocation: "" dataServiceAllocation: "" eventingServiceAllocation: "" indexServiceAllocation: "" name: "" requestedMemory: "" searchServiceAllocation: "" unusedMemory: "" unusedMemoryPercent: 0 autoscalers: - "" buckets: - compressionMode: "" conflictResolution: "" enableFlush: false enableIndexReplica: false evictionPolicy: "" ioPriority: "" memoryQuota: 0 name: "" password: "" replicas: 0 storageBackend: "" type: "" clusterId: "" conditions: - lastTransitionTime: "" lastUpdateTime: "" message: "" reason: "" status: "" type: "" controlPaused: false currentVersion: "" groups: - "" members: ready: - "" unready: - "" size: 0 users: - "" ``` ## [](#couchbaseclusters-apiversion)couchbaseclusters.apiVersion ### [](#constraints)Constraints **Type**: `string` ### [](#description)Description APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: . ## [](#couchbaseclusters-kind)couchbaseclusters.kind ### [](#constraints-2)Constraints **Type**: `string` ### [](#description-2)Description Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: . ## [](#couchbaseclusters-metadata)couchbaseclusters.metadata ### [](#constraints-3)Constraints **Required** **Type**: `object` ### [](#description-3)Description Standard object metadata as defined for all Kubernetes types. For additional details see the [Kubernetes reference documentation](https://kubernetes.io/docs/concepts/overview/working-with-objects/). ### [](#couchbaseclusters-metadata-name)couchbaseclusters.metadata.name #### [](#constraints-4)Constraints **Type**: `string` #### [](#description-4)Description The name of a resource. This must be unique for the kind of resource within the namespace. All resources must have a name. The name may be omitted and `metadata.generateName` used instead to generate a unique resource name. For additional details on resource names, see the [Kubernetes reference documentation](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/). ### [](#couchbaseclusters-metadata-namespace)couchbaseclusters.metadata.namespace #### [](#constraints-5)Constraints **Type**: `string` #### [](#description-5)Description The namespace the resource resides in. All resources reside in a namespace. The namespace is optional and may be specified in YAML configuration to override the namespace supplied by `kubectl`. For additional details on namespaces, see the [Kubernetes reference documentation](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/). ### [](#couchbaseclusters-metadata-labels)couchbaseclusters.metadata.labels #### [](#constraints-6)Constraints **Type**: `map[string]string` #### [](#description-6)Description Labels allow resources to be labeled with key/value pairs of data. Labels are indexed and allow resources to be selected based upon specified labels. Labels are relevant for certain types when using [label selection](../concept-label-selection.md) within your resources. For additional details on labels and selectors, see the [Kubernetes reference documentation](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/). ### [](#couchbaseclusters-metadata-annotations)couchbaseclusters.metadata.annotations #### [](#constraints-7)Constraints **Type**: `map[string]string` #### [](#description-7)Description Annotations allow resources to be annotated with key/value pairs of data. Annotations are arbitrary, and not indexed, so cannot be used to select resources, however may be used to add context or accounting to your resources. For additional details on annotations, see the [Kubernetes reference documentation](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/). ## [](#couchbaseclusters-spec)couchbaseclusters.spec ### [](#constraints-8)Constraints **Required** **Type**: `object` ### [](#description-8)Description ClusterSpec is the specification for a CouchbaseCluster resources, and allows the cluster to be customized. ### [](#couchbaseclusters-spec-antiaffinity)couchbaseclusters.spec.antiAffinity #### [](#constraints-9)Constraints **Type**: `boolean` #### [](#description-9)Description AntiAffinity forces the Operator to schedule different Couchbase server pods on different Kubernetes nodes. Anti-affinity reduces the likelihood of unrecoverable failure in the event of a node issue. Use of anti-affinity is highly recommended for production clusters. ### [](#couchbaseclusters-spec-autoresourceallocation)couchbaseclusters.spec.autoResourceAllocation #### [](#constraints-10)Constraints **Type**: `object` #### [](#description-10)Description AutoResourceAllocation populates pod resource requests based on the services running on that pod. When enabled, this feature will calculate the memory request as the total of service allocations defined in `spec.cluster`, plus an overhead defined by `spec.autoResourceAllocation.overheadPercent`.Changing individual allocations for a service will cause a cluster upgrade as allocations are modified in the underlying pods. This field also allows default pod CPU requests and limits to be applied. All resource allocations can be overridden by explicitly configuring them in the `spec.servers.resources` field. ### [](#couchbaseclusters-spec-autoresourceallocation-cpulimits)couchbaseclusters.spec.autoResourceAllocation.cpuLimits #### [](#constraints-11)Constraints **Type**: `string` **Default**: `4` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-11)Description CPULimits automatically populates the CPU limits across all Couchbase server pods. This field defaults to "4" CPUs. Explicitly specifying the CPU limit for a particular server class will override this value. More info: . ### [](#couchbaseclusters-spec-autoresourceallocation-cpurequests)couchbaseclusters.spec.autoResourceAllocation.cpuRequests #### [](#constraints-12)Constraints **Type**: `string` **Default**: `2` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-12)Description CPURequests automatically populates the CPU requests across all Couchbase server pods. The default value of "2", is the minimum recommended number of CPUs required to run Couchbase Server. Explicitly specifying the CPU request for a particular server class will override this value. More info: . ### [](#couchbaseclusters-spec-autoresourceallocation-enabled)couchbaseclusters.spec.autoResourceAllocation.enabled #### [](#constraints-13)Constraints **Type**: `boolean` #### [](#description-13)Description Enabled defines whether auto-resource allocation is enabled. ### [](#couchbaseclusters-spec-autoresourceallocation-overheadpercent)couchbaseclusters.spec.autoResourceAllocation.overheadPercent #### [](#constraints-14)Constraints **Type**: `integer` **Default**: `25` **Minimum**: `0` #### [](#description-14)Description OverheadPercent defines the amount of memory above that required for individual services on a pod. For Couchbase Server this should be approximately 25%. ### [](#couchbaseclusters-spec-autoscalestabilizationperiod)couchbaseclusters.spec.autoscaleStabilizationPeriod #### [](#constraints-15)Constraints **Type**: `string` #### [](#description-15)Description AutoscaleStabilizationPeriod defines how long after a rebalance the corresponding HorizontalPodAutoscaler should remain in maintenance mode. During maintenance mode all autoscaling is disabled since every HorizontalPodAutoscaler associated with the cluster becomes inactive. Since certain metrics can be unpredictable when Couchbase is rebalancing or upgrading, setting a stabilization period helps to prevent scaling recommendations from the HorizontalPodAutoscaler for a provided period of time. Values must be a valid Kubernetes duration of 0s or higher: A value of 0, puts the cluster in maintenance mode during rebalance but immediately exits this mode once the rebalance has completed. When undefined, the HPA is never put into maintenance mode during rebalance. ### [](#couchbaseclusters-spec-backup)couchbaseclusters.spec.backup #### [](#constraints-16)Constraints **Type**: `object` #### [](#description-16)Description Backup defines whether the Operator should manage automated backups, and how to lookup backup resources. ### [](#couchbaseclusters-spec-backup-annotations)couchbaseclusters.spec.backup.annotations #### [](#constraints-17)Constraints **Type**: `map[string]string` #### [](#description-17)Description Annotations defines additional annotations to appear on the backup/restore pods. ### [](#couchbaseclusters-spec-backup-image)couchbaseclusters.spec.backup.image #### [](#constraints-18)Constraints **Required** **Type**: `string` **Default**: `couchbase/operator-backup:1.3.1` #### [](#description-18)Description The Backup Image to run on backup pods. ### [](#couchbaseclusters-spec-backup-imagepullsecrets)couchbaseclusters.spec.backup.imagePullSecrets #### [](#constraints-19)Constraints **Type**: `[]object` #### [](#description-19)Description ImagePullSecrets allow you to use an image from private repositories and non-dockerhub ones. ### [](#couchbaseclusters-spec-backup-imagepullsecrets-name)couchbaseclusters.spec.backup.imagePullSecrets.name #### [](#constraints-20)Constraints **Type**: `string` #### [](#description-20)Description Name of the referent. More info: TODO: Add other useful fields. apiVersion, kind, uid?. ### [](#couchbaseclusters-spec-backup-labels)couchbaseclusters.spec.backup.labels #### [](#constraints-21)Constraints **Type**: `map[string]string` #### [](#description-21)Description Labels defines additional labels to appear on the backup/restore pods. ### [](#couchbaseclusters-spec-backup-managed)couchbaseclusters.spec.backup.managed #### [](#constraints-22)Constraints **Type**: `boolean` #### [](#description-22)Description Managed defines whether backups are managed by us or the clients. ### [](#couchbaseclusters-spec-backup-nodeselector)couchbaseclusters.spec.backup.nodeSelector #### [](#constraints-23)Constraints **Type**: `map[string]string` #### [](#description-23)Description NodeSelector defines which nodes to constrain the pods that run any backup and restore operations to. ### [](#couchbaseclusters-spec-backup-objectendpoint)couchbaseclusters.spec.backup.objectEndpoint #### [](#constraints-24)Constraints **Type**: `object` #### [](#description-24)Description Deprecated: by CouchbaseBackup.spec.objectStore.Endpoint ObjectEndpoint contains the configuration for connecting to a custom S3 compliant object store. ### [](#couchbaseclusters-spec-backup-objectendpoint-secret)couchbaseclusters.spec.backup.objectEndpoint.secret #### [](#constraints-25)Constraints **Type**: `string` #### [](#description-25)Description The name of the secret, in this namespace, that contains the CA certificate for verification of a TLS endpoint The secret must have the key with the name "tls.crt". ### [](#couchbaseclusters-spec-backup-objectendpoint-url)couchbaseclusters.spec.backup.objectEndpoint.url #### [](#constraints-26)Constraints **Type**: `string` #### [](#description-26)Description The host/address of the custom object endpoint. ### [](#couchbaseclusters-spec-backup-objectendpoint-usevirtualpath)couchbaseclusters.spec.backup.objectEndpoint.useVirtualPath #### [](#constraints-27)Constraints **Type**: `boolean` #### [](#description-27)Description UseVirtualPath will force the AWS SDK to use the new virtual style paths which are often required by S3 compatible object stores. ### [](#couchbaseclusters-spec-backup-resources)couchbaseclusters.spec.backup.resources #### [](#constraints-28)Constraints **Type**: `object` #### [](#description-28)Description Resources is the resource requirements for the backup and restore containers. Will be populated by defaults if not specified. ### [](#couchbaseclusters-spec-backup-s3secret)couchbaseclusters.spec.backup.s3Secret #### [](#constraints-29)Constraints **Type**: `string` #### [](#description-29)Description Deprecated: by CouchbaseBackup.spec.objectStore.secret S3Secret contains the key region and optionally access-key-id and secret-access-key for operating backups in S3\. This field must be popluated when the `spec.s3bucket` field is specified for a backup or restore resource. ### [](#couchbaseclusters-spec-backup-selector)couchbaseclusters.spec.backup.selector #### [](#constraints-30)Constraints **Type**: `object` #### [](#description-30)Description Selector allows CouchbaseBackup and CouchbaseBackupRestore resources to be filtered based on labels. ### [](#couchbaseclusters-spec-backup-serviceaccountname)couchbaseclusters.spec.backup.serviceAccountName #### [](#constraints-31)Constraints **Type**: `string` **Default**: `couchbase-backup` #### [](#description-31)Description The Service Account to run backup (and restore) pods under. Without this backup pods will not be able to update status. ### [](#couchbaseclusters-spec-backup-tolerations)couchbaseclusters.spec.backup.tolerations #### [](#constraints-32)Constraints **Type**: `[]object` #### [](#description-32)Description Tolerations specifies all backup and restore pod tolerations. ### [](#couchbaseclusters-spec-backup-tolerations-effect)couchbaseclusters.spec.backup.tolerations.effect #### [](#constraints-33)Constraints **Type**: `string` #### [](#description-33)Description Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute. ### [](#couchbaseclusters-spec-backup-tolerations-key)couchbaseclusters.spec.backup.tolerations.key #### [](#constraints-34)Constraints **Type**: `string` #### [](#description-34)Description Key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys. ### [](#couchbaseclusters-spec-backup-tolerations-operator)couchbaseclusters.spec.backup.tolerations.operator #### [](#constraints-35)Constraints **Type**: `string` #### [](#description-35)Description Operator represents a key's relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category. ### [](#couchbaseclusters-spec-backup-tolerations-tolerationseconds)couchbaseclusters.spec.backup.tolerations.tolerationSeconds #### [](#constraints-36)Constraints **Type**: `integer` #### [](#description-36)Description TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system. ### [](#couchbaseclusters-spec-backup-tolerations-value)couchbaseclusters.spec.backup.tolerations.value #### [](#constraints-37)Constraints **Type**: `string` #### [](#description-37)Description Value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string. ### [](#couchbaseclusters-spec-backup-useiamrole)couchbaseclusters.spec.backup.useIAMRole #### [](#constraints-38)Constraints **Type**: `boolean` #### [](#description-38)Description Deprecated: by CouchbaseBackup.spec.objectStore.useIAM UseIAMRole enables backup to fetch EC2 instance metadata. This allows the AWS SDK to use the EC2's IAM Role for S3 access. UseIAMRole will ignore credentials in s3Secret. ### [](#couchbaseclusters-spec-buckets)couchbaseclusters.spec.buckets #### [](#constraints-39)Constraints **Type**: `object` #### [](#description-39)Description Buckets defines whether the Operator should manage buckets, and how to lookup bucket resources. ### [](#couchbaseclusters-spec-buckets-managed)couchbaseclusters.spec.buckets.managed #### [](#constraints-40)Constraints **Type**: `boolean` #### [](#description-40)Description Managed defines whether buckets are managed by the Operator (true), or user managed (false). When Operator managed, all buckets must be defined with either CouchbaseBucket, CouchbaseEphemeralBucket or CouchbaseMemcachedBucket resources. Manual addition of buckets will be reverted by the Operator. When user managed, the Operator will not interrogate buckets at all. This field defaults to false. ### [](#couchbaseclusters-spec-buckets-selector)couchbaseclusters.spec.buckets.selector #### [](#constraints-41)Constraints **Type**: `object` #### [](#description-41)Description Selector is a label selector used to list buckets in the namespace that are managed by the Operator. ### [](#couchbaseclusters-spec-buckets-selector-matchexpressions)couchbaseclusters.spec.buckets.selector.matchExpressions #### [](#constraints-42)Constraints **Type**: `[]object` #### [](#description-42)Description matchExpressions is a list of label selector requirements. The requirements are ANDed. ### [](#couchbaseclusters-spec-buckets-selector-matchexpressions-key)couchbaseclusters.spec.buckets.selector.matchExpressions.key #### [](#constraints-43)Constraints **Required** **Type**: `string` #### [](#description-43)Description key is the label key that the selector applies to. ### [](#couchbaseclusters-spec-buckets-selector-matchexpressions-operator)couchbaseclusters.spec.buckets.selector.matchExpressions.operator #### [](#constraints-44)Constraints **Required** **Type**: `string` #### [](#description-44)Description operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist. ### [](#couchbaseclusters-spec-buckets-selector-matchexpressions-values)couchbaseclusters.spec.buckets.selector.matchExpressions.values #### [](#constraints-45)Constraints **Type**: `[]string` #### [](#description-45)Description values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch. ### [](#couchbaseclusters-spec-buckets-selector-matchlabels)couchbaseclusters.spec.buckets.selector.matchLabels #### [](#constraints-46)Constraints **Type**: `map[string]string` #### [](#description-46)Description matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is "key", the operator is "In", and the values array contains only "value". The requirements are ANDed. ### [](#couchbaseclusters-spec-buckets-synchronize)couchbaseclusters.spec.buckets.synchronize #### [](#constraints-47)Constraints **Type**: `boolean` #### [](#description-47)Description Synchronize allows unmanaged buckets, scopes, and collections to be synchronized as Kubernetes resources by the Operator. This feature is intended for development only and should not be used for production workloads. The synchronization workflow starts with `spec.buckets.managed` being set to false, the user can manually create buckets, scopes, and collections using the Couchbase UI, or other tooling. When you wish to commit to Kubernetes resources, you must specify a unique label selector in the `spec.buckets.selector` field, and this field is set to true. The Operator will create Kubernetes resources for you, and upon completion set the cluster's `Synchronized`status condition. Synchronizing will not create a Kubernetes resource for the Couchbase Server maintained \_system scope. You may then safely set `spec.buckets.managed` to true and the Operator will manage these resources as per usual. To update an already managed data topology, you must first set it to unmanaged, make any changes, and delete any old resources, then follow the standard synchronization workflow. The Operator can not, and will not, ever delete, or make modifications to resource specifications that are intended to be user managed, or managed by a life cycle management tool. These actions must be instigated by an end user. For a more complete experience, refer to the documentation for the `cao save` and `cao restore` CLI commands. ### [](#couchbaseclusters-spec-cluster)couchbaseclusters.spec.cluster #### [](#constraints-48)Constraints **Type**: `object` **Default**: `{}` #### [](#description-48)Description ClusterSettings define Couchbase cluster-wide settings such as memory allocation, failover characteristics and index settings. ### [](#couchbaseclusters-spec-cluster-analyticsservicememoryquota)couchbaseclusters.spec.cluster.analyticsServiceMemoryQuota #### [](#constraints-49)Constraints **Type**: `string` **Default**: `1Gi` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-49)Description AnalyticsServiceMemQuota is the amount of memory that should be allocated to the analytics service. This value is per-pod, and only applicable to pods belonging to server classes running the analytics service. This field must be a quantity greater than or equal to 1Gi. This field defaults to 1Gi. More info: . ### [](#couchbaseclusters-spec-cluster-autocompaction)couchbaseclusters.spec.cluster.autoCompaction #### [](#constraints-50)Constraints **Type**: `object` **Default**: `{}` #### [](#description-50)Description AutoCompaction allows the configuration of auto-compaction, including on what conditions disk space is reclaimed and when it is allowed to run. ### [](#couchbaseclusters-spec-cluster-autocompaction-databasefragmentationthreshold)couchbaseclusters.spec.cluster.autoCompaction.databaseFragmentationThreshold #### [](#constraints-51)Constraints **Type**: `object` **Default**: `{}` #### [](#description-51)Description DatabaseFragmentationThreshold defines triggers for when database compaction should start. ### [](#couchbaseclusters-spec-cluster-autocompaction-databasefragmentationthreshold-percent)couchbaseclusters.spec.cluster.autoCompaction.databaseFragmentationThreshold.percent #### [](#constraints-52)Constraints **Type**: `integer` **Default**: `30` **Minimum**: `2` **Maximum**: `100` #### [](#description-52)Description Percent is the percentage of disk fragmentation after which to decompaction will be triggered. This field must be in the range 2-100, defaulting to 30. ### [](#couchbaseclusters-spec-cluster-autocompaction-databasefragmentationthreshold-size)couchbaseclusters.spec.cluster.autoCompaction.databaseFragmentationThreshold.size #### [](#constraints-53)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-53)Description Size is the amount of disk framentation, that once exceeded, will trigger decompaction. More info: . ### [](#couchbaseclusters-spec-cluster-autocompaction-parallelcompaction)couchbaseclusters.spec.cluster.autoCompaction.parallelCompaction #### [](#constraints-54)Constraints **Type**: `boolean` #### [](#description-54)Description ParallelCompaction controls whether database and view compactions can happen in parallel. ### [](#couchbaseclusters-spec-cluster-autocompaction-timewindow)couchbaseclusters.spec.cluster.autoCompaction.timeWindow #### [](#constraints-55)Constraints **Type**: `object` #### [](#description-55)Description TimeWindow allows restriction of when compaction can occur. ### [](#couchbaseclusters-spec-cluster-autocompaction-timewindow-abortcompactionoutsidewindow)couchbaseclusters.spec.cluster.autoCompaction.timeWindow.abortCompactionOutsideWindow #### [](#constraints-56)Constraints **Type**: `boolean` **Default**: `False` #### [](#description-56)Description AbortCompactionOutsideWindow stops compaction processes when the process moves outside the window. ### [](#couchbaseclusters-spec-cluster-autocompaction-timewindow-end)couchbaseclusters.spec.cluster.autoCompaction.timeWindow.end #### [](#constraints-57)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(2[0-3]|[01]?[0-9]):([0-5]?[0-9])$` #### [](#description-57)Description End is a wallclock time, in the form HH:MM, when a compaction should stop. ### [](#couchbaseclusters-spec-cluster-autocompaction-timewindow-start)couchbaseclusters.spec.cluster.autoCompaction.timeWindow.start #### [](#constraints-58)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(2[0-3]|[01]?[0-9]):([0-5]?[0-9])$` #### [](#description-58)Description Start is a wallclock time, in the form HH:MM, when a compaction is permitted to start. ### [](#couchbaseclusters-spec-cluster-autocompaction-tombstonepurgeinterval)couchbaseclusters.spec.cluster.autoCompaction.tombstonePurgeInterval #### [](#constraints-59)Constraints **Type**: `string` **Default**: `72h` #### [](#description-59)Description TombstonePurgeInterval controls how long to wait before purging tombstones. This field must be in the range 1h-1440h, defaulting to 72h. More info: . ### [](#couchbaseclusters-spec-cluster-autocompaction-viewfragmentationthreshold)couchbaseclusters.spec.cluster.autoCompaction.viewFragmentationThreshold #### [](#constraints-60)Constraints **Type**: `object` **Default**: `{}` #### [](#description-60)Description ViewFragmentationThreshold defines triggers for when view compaction should start. ### [](#couchbaseclusters-spec-cluster-autocompaction-viewfragmentationthreshold-percent)couchbaseclusters.spec.cluster.autoCompaction.viewFragmentationThreshold.percent #### [](#constraints-61)Constraints **Type**: `integer` **Default**: `30` **Minimum**: `2` **Maximum**: `100` #### [](#description-61)Description Percent is the percentage of disk fragmentation after which to decompaction will be triggered. This field must be in the range 2-100, defaulting to 30. ### [](#couchbaseclusters-spec-cluster-autocompaction-viewfragmentationthreshold-size)couchbaseclusters.spec.cluster.autoCompaction.viewFragmentationThreshold.size #### [](#constraints-62)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-62)Description Size is the amount of disk framentation, that once exceeded, will trigger decompaction. More info: . ### [](#couchbaseclusters-spec-cluster-autofailovermaxcount)couchbaseclusters.spec.cluster.autoFailoverMaxCount #### [](#constraints-63)Constraints **Type**: `integer` **Default**: `1` **Minimum**: `1` #### [](#description-63)Description AutoFailoverMaxCount is the maximum number of automatic failovers Couchbase server will allow before not allowing any more. This field must be between 1-3 for server versions prior to 7.1.0 default is 1. ### [](#couchbaseclusters-spec-cluster-autofailoverondatadiskissues)couchbaseclusters.spec.cluster.autoFailoverOnDataDiskIssues #### [](#constraints-64)Constraints **Type**: `boolean` #### [](#description-64)Description AutoFailoverOnDataDiskIssues defines whether Couchbase server should failover a pod if a disk issue was detected. ### [](#couchbaseclusters-spec-cluster-autofailoverondatadiskissuestimeperiod)couchbaseclusters.spec.cluster.autoFailoverOnDataDiskIssuesTimePeriod #### [](#constraints-65)Constraints **Type**: `string` **Default**: `120s` #### [](#description-65)Description AutoFailoverOnDataDiskIssuesTimePeriod defines how long to wait for transient errors before failing over a faulty disk. This field must be in the range 5-3600s, defaulting to 120s. More info: . ### [](#couchbaseclusters-spec-cluster-autofailoverservergroup)couchbaseclusters.spec.cluster.autoFailoverServerGroup #### [](#constraints-66)Constraints **Type**: `boolean` #### [](#description-66)Description AutoFailoverServerGroup whether to enable failing over a server group. This field is ignored in server versions 7.1+ as it has been removed from the Couchbase API. ### [](#couchbaseclusters-spec-cluster-autofailovertimeout)couchbaseclusters.spec.cluster.autoFailoverTimeout #### [](#constraints-67)Constraints **Type**: `string` **Default**: `120s` #### [](#description-67)Description AutoFailoverTimeout defines how long Couchbase server will wait between a pod being witnessed as down, until when it will failover the pod. Couchbase server will only failover pods if it deems it safe to do so, and not result in data loss. This field must be in the range 5-3600s, defaulting to 120s. More info: . ### [](#couchbaseclusters-spec-cluster-clustername)couchbaseclusters.spec.cluster.clusterName #### [](#constraints-68)Constraints **Type**: `string` #### [](#description-68)Description ClusterName defines the name of the cluster, as displayed in the Couchbase UI. By default, the cluster name is that specified in the CouchbaseCluster resource's metadata. ### [](#couchbaseclusters-spec-cluster-data)couchbaseclusters.spec.cluster.data #### [](#constraints-69)Constraints **Type**: `object` #### [](#description-69)Description Data allows the data service to be configured. ### [](#couchbaseclusters-spec-cluster-data-auxiothreads)couchbaseclusters.spec.cluster.data.auxIOThreads #### [](#constraints-70)Constraints **Type**: `integer` **Minimum**: `1` **Maximum**: `64` #### [](#description-70)Description AuxIOThreads allows the number of threads used by the data service, per pod, to be altered. This indicates the number of threads that are to be used in the AuxIO thread pool to run auxiliary I/O tasks. This value must be between 1 and 64 threads and is only supported on CB versions 7.1.0+. and should only be increased where there are sufficient CPU resources allocated for their use. If not specified, this defaults to the default value set by Couchbase Server. ### [](#couchbaseclusters-spec-cluster-data-minreplicascount)couchbaseclusters.spec.cluster.data.minReplicasCount #### [](#constraints-71)Constraints **Type**: `integer` **Default**: `0` #### [](#description-71)Description MinReplicasCount allows the minimum number of replicas required for buckets to be set. New buckets cannot be created with less than this minimum. Defaults to 0. ### [](#couchbaseclusters-spec-cluster-data-noniothreads)couchbaseclusters.spec.cluster.data.nonIOThreads #### [](#constraints-72)Constraints **Type**: `integer` **Minimum**: `1` **Maximum**: `64` #### [](#description-72)Description NonIOThreads allows the number of threads used by the data service, per pod, to be altered. This indicates the number of threads that are to be used in the NonIO thread pool to run in memory tasks. This value must be between 1 and 64 threads and is only supported on CB versions 7.1.0+. and should only be increased where there are sufficient CPU resources allocated for their use. If not specified, this defaults to the default value set by Couchbase Server. ### [](#couchbaseclusters-spec-cluster-data-readerthreads)couchbaseclusters.spec.cluster.data.readerThreads #### [](#constraints-73)Constraints **Type**: `integer` **Minimum**: `1` **Maximum**: `64` #### [](#description-73)Description ReaderThreads allows the number of threads used by the data service, per pod, to be altered. This value must be between 4 and 64 threads for CB versions below 7.1.0 and, or 1 and 64 for CB versions 7.1.0+. and should only be increased where there are sufficient CPU resources allocated for their use. If not specified, this defaults to the default value set by Couchbase Server. ### [](#couchbaseclusters-spec-cluster-data-writerthreads)couchbaseclusters.spec.cluster.data.writerThreads #### [](#constraints-74)Constraints **Type**: `integer` **Minimum**: `1` **Maximum**: `64` #### [](#description-74)Description WriterThreads allows the number of threads used by the data service, per pod, to be altered. This setting is especially relevant when using "durable writes", increasing this field will have a large impact on performance. This value must be between 4 and 64 threads for CB versions below 7.1.0 and, // or 1 and 64 for CB versions 7.1.0+. and should only be increased where there are sufficient CPU resources allocated for their use. If not specified, this defaults to the default value set by Couchbase Server. ### [](#couchbaseclusters-spec-cluster-dataservicememoryquota)couchbaseclusters.spec.cluster.dataServiceMemoryQuota #### [](#constraints-75)Constraints **Type**: `string` **Default**: `256Mi` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-75)Description DataServiceMemQuota is the amount of memory that should be allocated to the data service. This value is per-pod, and only applicable to pods belonging to server classes running the data service. This field must be a quantity greater than or equal to 256Mi. This field defaults to 256Mi. More info: . ### [](#couchbaseclusters-spec-cluster-eventingservicememoryquota)couchbaseclusters.spec.cluster.eventingServiceMemoryQuota #### [](#constraints-76)Constraints **Type**: `string` **Default**: `256Mi` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-76)Description EventingServiceMemQuota is the amount of memory that should be allocated to the eventing service. This value is per-pod, and only applicable to pods belonging to server classes running the eventing service. This field must be a quantity greater than or equal to 256Mi. This field defaults to 256Mi. More info: . ### [](#couchbaseclusters-spec-cluster-indexservicememoryquota)couchbaseclusters.spec.cluster.indexServiceMemoryQuota #### [](#constraints-77)Constraints **Type**: `string` **Default**: `256Mi` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-77)Description IndexServiceMemQuota is the amount of memory that should be allocated to the index service. This value is per-pod, and only applicable to pods belonging to server classes running the index service. This field must be a quantity greater than or equal to 256Mi. This field defaults to 256Mi. More info: . ### [](#couchbaseclusters-spec-cluster-indexstoragesetting)couchbaseclusters.spec.cluster.indexStorageSetting #### [](#constraints-78)Constraints **Type**: `string` **Default**: `memory_optimized` **Enumerations**: `memory_optimized, plasma` #### [](#description-78)Description **DEPRECATED** \- by indexer. The index storage mode to use for secondary indexing. This field must be one of "memory\_optimized" or "plasma", defaulting to "memory\_optimized". This field is immutable and cannot be changed unless there are no server classes running the index service in the cluster. ### [](#couchbaseclusters-spec-cluster-indexer)couchbaseclusters.spec.cluster.indexer #### [](#constraints-79)Constraints **Type**: `object` #### [](#description-79)Description Indexer allows the indexer to be configured. ### [](#couchbaseclusters-spec-cluster-indexer-enableshardaffinity)couchbaseclusters.spec.cluster.indexer.enableShardAffinity #### [](#constraints-80)Constraints **Type**: `boolean` **Default**: `False` #### [](#description-80)Description EnableShardAffinity when false Index Servers rebuild any index that are newly assigned to them during a rebalance. When set to true, Couchbase Server moves a reassigned index's files between Index Servers. This field is only supported on CB versions 7.6.0+. ### [](#couchbaseclusters-spec-cluster-indexer-loglevel)couchbaseclusters.spec.cluster.indexer.logLevel #### [](#constraints-81)Constraints **Type**: `string` **Default**: `info` **Enumerations**: `silent, fatal, error, warn, info, verbose, timing, debug, trace` #### [](#description-81)Description LogLevel controls the verbosity of indexer logs. This field must be one of "silent", "fatal", "error", "warn", "info", "verbose", "timing", "debug" or "trace", defaulting to "info". ### [](#couchbaseclusters-spec-cluster-indexer-maxrollbackpoints)couchbaseclusters.spec.cluster.indexer.maxRollbackPoints #### [](#constraints-82)Constraints **Type**: `integer` **Default**: `2` **Minimum**: `1` #### [](#description-82)Description MaxRollbackPoints controls the number of checkpoints that can be rolled back to. The default is 2, with a minimum of 1. ### [](#couchbaseclusters-spec-cluster-indexer-memorysnapshotinterval)couchbaseclusters.spec.cluster.indexer.memorySnapshotInterval #### [](#constraints-83)Constraints **Type**: `string` **Default**: `200ms` #### [](#description-83)Description MemorySnapshotInterval controls when memory indexes should be snapshotted. This defaults to 200ms, and must be greater than or equal to 1ms. ### [](#couchbaseclusters-spec-cluster-indexer-numreplica)couchbaseclusters.spec.cluster.indexer.numReplica #### [](#constraints-84)Constraints **Type**: `integer` **Default**: `0` **Minimum**: `0` #### [](#description-84)Description NumberOfReplica specifies number of secondary index replicas to be created by the Index Service whenever CREATE INDEX is invoked, which ensures high availability and high performance. Note, if nodes and num\_replica are both specified in the WITH clause, the specified number of nodes must be one greater than num\_replica This defaults to 0, which means no index replicas to be created by default. Minimum must be 0. ### [](#couchbaseclusters-spec-cluster-indexer-redistributeindexes)couchbaseclusters.spec.cluster.indexer.redistributeIndexes #### [](#constraints-85)Constraints **Type**: `boolean` **Default**: `False` #### [](#description-85)Description RedistributeIndexes when true, Couchbase Server redistributes indexes when rebalance occurs, in order to optimize performance. If false (the default), such redistribution does not occur. ### [](#couchbaseclusters-spec-cluster-indexer-stablesnapshotinterval)couchbaseclusters.spec.cluster.indexer.stableSnapshotInterval #### [](#constraints-86)Constraints **Type**: `string` **Default**: `5s` #### [](#description-86)Description StableSnapshotInterval controls when disk indexes should be snapshotted. This defaults to 5s, and must be greater than or equal to 1ms. ### [](#couchbaseclusters-spec-cluster-indexer-storagemode)couchbaseclusters.spec.cluster.indexer.storageMode #### [](#constraints-87)Constraints **Type**: `string` **Default**: `memory_optimized` **Enumerations**: `memory_optimized, plasma` #### [](#description-87)Description StorageMode controls the underlying storage engine for indexes. Once set it can only be modified if there are no nodes in the cluster running the index service. The field must be one of "memory\_optimized" or "plasma", defaulting to "memory\_optimized". ### [](#couchbaseclusters-spec-cluster-indexer-threads)couchbaseclusters.spec.cluster.indexer.threads #### [](#constraints-88)Constraints **Type**: `integer` **Minimum**: `0` #### [](#description-88)Description Threads controls the number of processor threads to use for indexing. A value of 0 means 1 per CPU. This attribute must be greater than or equal to 0, defaulting to 0. ### [](#couchbaseclusters-spec-cluster-query)couchbaseclusters.spec.cluster.query #### [](#constraints-89)Constraints **Type**: `object` #### [](#description-89)Description Query allows the query service to be configured. ### [](#couchbaseclusters-spec-cluster-query-backfillenabled)couchbaseclusters.spec.cluster.query.backfillEnabled #### [](#constraints-90)Constraints **Type**: `boolean` **Default**: `True` #### [](#description-90)Description BackfillEnabled allows the query service to backfill. ### [](#couchbaseclusters-spec-cluster-query-cboenabled)couchbaseclusters.spec.cluster.query.cboEnabled #### [](#constraints-91)Constraints **Required** **Type**: `boolean` **Default**: `True` #### [](#description-91)Description CBOEnabled specifies whether the cost-based optimizer is enabled. Defaults to true. ### [](#couchbaseclusters-spec-cluster-query-cleanupclientattemptsenabled)couchbaseclusters.spec.cluster.query.cleanupClientAttemptsEnabled #### [](#constraints-92)Constraints **Required** **Type**: `boolean` **Default**: `True` #### [](#description-92)Description CleanupClientAttemptsEnabled specifies whether the Query service preferentially aims to clean up just transactions that it has created, leaving transactions for the distributed cleanup process only when it is forced to. Defaults to true. ### [](#couchbaseclusters-spec-cluster-query-cleanuplostattemptsenabled)couchbaseclusters.spec.cluster.query.cleanupLostAttemptsEnabled #### [](#constraints-93)Constraints **Required** **Type**: `boolean` **Default**: `True` #### [](#description-93)Description CleanupLostAttemptsEnabled specifies the Query service takes part in the distributed cleanup process, and cleans up expired transactions created by any client. Defaults to true. ### [](#couchbaseclusters-spec-cluster-query-cleanupwindow)couchbaseclusters.spec.cluster.query.cleanupWindow #### [](#constraints-94)Constraints **Required** **Type**: `string` **Default**: `60s` #### [](#description-94)Description CleanupWindow specifies how frequently the Query service checks its subset of active transaction records for cleanup. Defaults to 60s. ### [](#couchbaseclusters-spec-cluster-query-completedlimit)couchbaseclusters.spec.cluster.query.completedLimit #### [](#constraints-95)Constraints **Required** **Type**: `integer` **Default**: `4000` #### [](#description-95)Description CompletedLimit sets the number of requests to be logged in the completed requests catalog. As new completed requests are added, old ones are removed. ### [](#couchbaseclusters-spec-cluster-query-completedmaxplansize)couchbaseclusters.spec.cluster.query.completedMaxPlanSize #### [](#constraints-96)Constraints **Required** **Type**: `string` **Default**: `262144` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-96)Description CompletedMaxPlanSize limits the size of query execution plans that can be logged in the completed requests catalog. Queries with plans larger than this are not logged. This field is only supported on CB versions 7.6.0+. Defaults to 262144, maximum value is 20840448, and minimum value is 0. ### [](#couchbaseclusters-spec-cluster-query-completedtrackingallrequests)couchbaseclusters.spec.cluster.query.completedTrackingAllRequests #### [](#constraints-97)Constraints **Required** **Type**: `boolean` **Default**: `False` #### [](#description-97)Description CompletedTrackingAllRequests allows all requests to be tracked regardless of their time. This field requires `completedTrackingEnabled` to be true. ### [](#couchbaseclusters-spec-cluster-query-completedtrackingenabled)couchbaseclusters.spec.cluster.query.completedTrackingEnabled #### [](#constraints-98)Constraints **Required** **Type**: `boolean` **Default**: `True` #### [](#description-98)Description CompletedTrackingEnabled allows completed requests to be tracked in the requests catalog. ### [](#couchbaseclusters-spec-cluster-query-completedtrackingthreshold)couchbaseclusters.spec.cluster.query.completedTrackingThreshold #### [](#constraints-99)Constraints **Type**: `string` **Default**: `7s` #### [](#description-99)Description CompletedThreshold is a trigger for queries to be logged in the completed requests catalog. All completed queries lasting longer than this threshold are logged in the completed requests catalog. This field requires `completedTrackingEnabled`to be set to true and `completedTrackingAllRequests` to be false to have any effect. ### [](#couchbaseclusters-spec-cluster-query-loglevel)couchbaseclusters.spec.cluster.query.logLevel #### [](#constraints-100)Constraints **Type**: `string` **Default**: `info` **Enumerations**: `debug, trace, info, warn, error, severe, none` #### [](#description-100)Description LogLevel controls the verbosity of query logs. This field must be one of "debug", "trace", "info", "warn", "error", "severe", or "none", defaulting to "info". ### [](#couchbaseclusters-spec-cluster-query-maxparallelism)couchbaseclusters.spec.cluster.query.maxParallelism #### [](#constraints-101)Constraints **Required** **Type**: `integer` **Default**: `1` #### [](#description-101)Description MaxParallelism specifies the maximum parallelism for queries on all Query nodes in the cluster. If the value is zero, negative, or larger than the number of allowed cored the maximum parallelism is restricted to the number of allowed cores. Defaults to 1. ### [](#couchbaseclusters-spec-cluster-query-memoryquota)couchbaseclusters.spec.cluster.query.memoryQuota #### [](#constraints-102)Constraints **Type**: `string` **Default**: `0` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-102)Description MemoryQuota specifies the maximum amount of memory a request may use on any Query node in the cluster. This parameter enforces a ceiling on the memory used for the tracked documents required for processing a request. It does not take into account any other memory that might be used to process a request, such as the stack, the operators, or some intermediate values. Defaults to 0. ### [](#couchbaseclusters-spec-cluster-query-nodequotavalpercent)couchbaseclusters.spec.cluster.query.nodeQuotaValPercent #### [](#constraints-103)Constraints **Required** **Type**: `integer` **Default**: `67` **Minimum**: `0` **Maximum**: `100` #### [](#description-103)Description NodeQuotaValPercent sets the percentage of the `useReplica` that is dedicated to tracked value content memory across all active requests for every Query node in the cluster. This field is only supported on CB versions 7.6.0+. Defaults to 67. ### [](#couchbaseclusters-spec-cluster-query-numactivetransactionrecords)couchbaseclusters.spec.cluster.query.numActiveTransactionRecords #### [](#constraints-104)Constraints **Required** **Type**: `integer` **Default**: `1024` **Minimum**: `1` #### [](#description-104)Description NumActiveTransactionRecords specifies the total number of active transaction records for all Query nodes in the cluster. Default to 1024 and has a minimum of 1. ### [](#couchbaseclusters-spec-cluster-query-numcpus)couchbaseclusters.spec.cluster.query.numCpus #### [](#constraints-105)Constraints **Required** **Type**: `integer` **Default**: `0` **Minimum**: `0` #### [](#description-105)Description NumCpus is the number of CPUs the Query service can use on any Query node in the cluster. When set to 0 (the default), the Query service can use all available CPUs, up to the limits described below. The number of CPUs can never be greater than the number of logical CPUs. In Community Edition, the number of allowed CPUs cannot be greater than 4\. In Enterprise Edition, there is no limit to the number of allowed CPUs. This field is only supported on CB versions 7.6.0+. NOTE: This change requires a restart of the Query service to take effect which can be done by rescheduling nodes that are running the query service. Defaults to 0. ### [](#couchbaseclusters-spec-cluster-query-pipelinebatch)couchbaseclusters.spec.cluster.query.pipelineBatch #### [](#constraints-106)Constraints **Required** **Type**: `integer` **Default**: `16` #### [](#description-106)Description PipelineBatch controls the number of items execution operators can batch for Fetch from the KV. Defaults to 16. ### [](#couchbaseclusters-spec-cluster-query-pipelinecap)couchbaseclusters.spec.cluster.query.pipelineCap #### [](#constraints-107)Constraints **Required** **Type**: `integer` **Default**: `512` #### [](#description-107)Description PipelineCap controls the maximum number of items each execution operator can buffer between various operators. Defaults to 512. ### [](#couchbaseclusters-spec-cluster-query-preparedlimit)couchbaseclusters.spec.cluster.query.preparedLimit #### [](#constraints-108)Constraints **Required** **Type**: `integer` **Default**: `16384` #### [](#description-108)Description PreparedLimit is the maximum number of prepared statements in the cache. When this cache reaches the limit, the least recently used prepared statements will be discarded as new prepared statements are created. ### [](#couchbaseclusters-spec-cluster-query-scancap)couchbaseclusters.spec.cluster.query.scanCap #### [](#constraints-109)Constraints **Required** **Type**: `integer` **Default**: `512` #### [](#description-109)Description ScapCan sets the maximum buffered channel size between the indexer client and the query service for index scans. Defaults to 512. ### [](#couchbaseclusters-spec-cluster-query-temporaryspace)couchbaseclusters.spec.cluster.query.temporarySpace #### [](#constraints-110)Constraints **Type**: `string` **Default**: `5Gi` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-110)Description TemporarySpace allows the temporary storage used by the query service backfill, per-pod, to be modified. This field requires `backfillEnabled` to be set to true in order to have any effect. More info: . ### [](#couchbaseclusters-spec-cluster-query-temporaryspaceunlimited)couchbaseclusters.spec.cluster.query.temporarySpaceUnlimited #### [](#constraints-111)Constraints **Type**: `boolean` #### [](#description-111)Description TemporarySpaceUnlimited allows the temporary storage used by the query service backfill, per-pod, to be unconstrained. This field requires `backfillEnabled` to be set to true in order to have any effect. This field overrides `temporarySpace`. ### [](#couchbaseclusters-spec-cluster-query-timeout)couchbaseclusters.spec.cluster.query.timeout #### [](#constraints-112)Constraints **Type**: `string` #### [](#description-112)Description Timeout is the maximum time to spend on the request before timing out. If this field is not set then there will be no timeout. ### [](#couchbaseclusters-spec-cluster-query-txtimeout)couchbaseclusters.spec.cluster.query.txTimeout #### [](#constraints-113)Constraints **Type**: `string` **Default**: `0ms` #### [](#description-113)Description TxTimeout is the maximum time to spend on a transaction before timing out. This setting only applies to requests containing the BEGIN TRANSACTION statement, or to requests where the tximplicit parameter is set. For all other requests, it is ignored. Defaults to 0ms (no timeout). ### [](#couchbaseclusters-spec-cluster-query-usereplica)couchbaseclusters.spec.cluster.query.useReplica #### [](#constraints-114)Constraints **Type**: `boolean` #### [](#description-114)Description UseReplica specifies whether a query can fetch data from a replica vBucket if active vBuckets are inaccessible. If set to true then read from replica is enabled for all queries, but can be disabled at request level. If set to false read from replica is disabled for all queries and cannot be overridden at request level. If this field is unset then it is enabled/disabled at the request level. This field is only supported on CB versions 7.6.0+. ### [](#couchbaseclusters-spec-cluster-queryservicememoryquota)couchbaseclusters.spec.cluster.queryServiceMemoryQuota #### [](#constraints-115)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-115)Description QueryServiceMemQuota is used when the spec.autoResourceAllocation feature is enabled, and is used to define the amount of memory reserved by the query service for use with Kubernetes resource scheduling. More info: In CB Server 7.6.0+ QueryServiceMemQuota also sets a soft memory limit for every Query node in the cluster. The garbage collector tries to keep below this target. It is not a hard, absolute limit, and memory usage may exceed this value. ### [](#couchbaseclusters-spec-cluster-searchservicememoryquota)couchbaseclusters.spec.cluster.searchServiceMemoryQuota #### [](#constraints-116)Constraints **Type**: `string` **Default**: `256Mi` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-116)Description SearchServiceMemQuota is the amount of memory that should be allocated to the search service. This value is per-pod, and only applicable to pods belonging to server classes running the search service. This field must be a quantity greater than or equal to 256Mi. This field defaults to 256Mi. More info: . ### [](#couchbaseclusters-spec-enableonlinevolumeexpansion)couchbaseclusters.spec.enableOnlineVolumeExpansion #### [](#constraints-117)Constraints **Type**: `boolean` #### [](#description-117)Description EnableOnlineVolumeExpansion enables online expansion of Persistent Volumes. You can only expand a PVC if its storage class's "allowVolumeExpansion" field is set to true. Additionally, Kubernetes feature "ExpandInUsePersistentVolumes" must be enabled in order to expand the volumes which are actively bound to Pods. Volumes can only be expanded and not reduced to a smaller size. See: If "EnableOnlineVolumeExpansion" is enabled for use within an environment that does not actually support online volume and file system expansion then the cluster will fallback to rolling upgrade procedure to create a new set of Pods for use with resized Volumes. More info: . ### [](#couchbaseclusters-spec-enablepreviewscaling)couchbaseclusters.spec.enablePreviewScaling #### [](#constraints-118)Constraints **Type**: `boolean` #### [](#description-118)Description **DEPRECATED** \- This option only exists for backwards compatibility and no longer restricts autoscaling to ephemeral services. EnablePreviewScaling enables autoscaling for stateful services and buckets. ### [](#couchbaseclusters-spec-envimageprecedence)couchbaseclusters.spec.envImagePrecedence #### [](#constraints-119)Constraints **Type**: `boolean` #### [](#description-119)Description EnvImagePrecedence gives precedence over the default container image name in `spec.Image` to an image name provided through Operator environment variables. For more info on using Operator environment variables: . ### [](#couchbaseclusters-spec-hibernate)couchbaseclusters.spec.hibernate #### [](#constraints-120)Constraints **Type**: `boolean` #### [](#description-120)Description Hibernate is whether to hibernate the cluster. ### [](#couchbaseclusters-spec-hibernationstrategy)couchbaseclusters.spec.hibernationStrategy #### [](#constraints-121)Constraints **Type**: `string` **Enumerations**: `Immediate` #### [](#description-121)Description HibernationStrategy defines how to hibernate the cluster. When Immediate the Operator will immediately delete all pods and take no further action until the hibernate field is set to false. ### [](#couchbaseclusters-spec-image)couchbaseclusters.spec.image #### [](#constraints-122)Constraints **Required** **Type**: `string` **Pattern (Regular Expression)**: `^(.*?(:\d+)?/)?.\*?/.*?(:.\*?\d+\.\d+\.\d+.\*|@sha256:[0-9a-f]{64})$` #### [](#description-122)Description Image is the container image name that will be used to launch Couchbase server instances. Updating this field will cause an automatic upgrade of the cluster. Explicitly specifying the image for a server class will override this value for the server class. ### [](#couchbaseclusters-spec-logging)couchbaseclusters.spec.logging #### [](#constraints-123)Constraints **Type**: `object` #### [](#description-123)Description Logging defines Operator logging options. ### [](#couchbaseclusters-spec-logging-audit)couchbaseclusters.spec.logging.audit #### [](#constraints-124)Constraints **Type**: `object` #### [](#description-124)Description Used to manage the audit configuration directly. ### [](#couchbaseclusters-spec-logging-audit-disabledevents)couchbaseclusters.spec.logging.audit.disabledEvents #### [](#constraints-125)Constraints **Type**: `[]integer` #### [](#description-125)Description The list of event ids to disable for auditing purposes. This is passed to the REST API with no verification by the operator. Refer to the documentation for details: . ### [](#couchbaseclusters-spec-logging-audit-disabledusers)couchbaseclusters.spec.logging.audit.disabledUsers #### [](#constraints-126)Constraints **Type**: `[]string` **Pattern (Regular Expression)**: `^.+/(local|external)$` #### [](#description-126)Description The list of users to ignore for auditing purposes. This is passed to the REST API with minimal validation it meets an acceptable regex pattern. Refer to the documentation for full details on how to configure this: . ### [](#couchbaseclusters-spec-logging-audit-enabled)couchbaseclusters.spec.logging.audit.enabled #### [](#constraints-127)Constraints **Type**: `boolean` #### [](#description-127)Description Enabled is a boolean that enables the audit capabilities. ### [](#couchbaseclusters-spec-logging-audit-garbagecollection)couchbaseclusters.spec.logging.audit.garbageCollection #### [](#constraints-128)Constraints **Type**: `object` #### [](#description-128)Description Handle all optional garbage collection (GC) configuration for the audit functionality. This is not part of the audit REST API, it is intended to handle GC automatically for the audit logs. By default the Couchbase Server rotates the audit logs but does not clean up the rotated logs. This is left as an operation for the cluster administrator to manage, the operator allows for us to automate this: . ### [](#couchbaseclusters-spec-logging-audit-garbagecollection-sidecar)couchbaseclusters.spec.logging.audit.garbageCollection.sidecar #### [](#constraints-129)Constraints **Type**: `object` #### [](#description-129)Description **DEPRECATED** \- by spec.logging.audit.rotation for Couchbase Server 7.2.4+ Provide the sidecar configuration required (if so desired) to automatically clean up audit logs. ### [](#couchbaseclusters-spec-logging-audit-garbagecollection-sidecar-age)couchbaseclusters.spec.logging.audit.garbageCollection.sidecar.age #### [](#constraints-130)Constraints **Type**: `string` **Default**: `1h` #### [](#description-130)Description The minimum age of rotated log files to remove, defaults to one hour. ### [](#couchbaseclusters-spec-logging-audit-garbagecollection-sidecar-enabled)couchbaseclusters.spec.logging.audit.garbageCollection.sidecar.enabled #### [](#constraints-131)Constraints **Type**: `boolean` #### [](#description-131)Description Enable this sidecar by setting to true, defaults to being disabled. ### [](#couchbaseclusters-spec-logging-audit-garbagecollection-sidecar-image)couchbaseclusters.spec.logging.audit.garbageCollection.sidecar.image #### [](#constraints-132)Constraints **Type**: `string` **Default**: `busybox:1.33.1` #### [](#description-132)Description Image is the image to be used to run the audit sidecar helper. No validation is carried out as this can be any arbitrary repo and tag. ### [](#couchbaseclusters-spec-logging-audit-garbagecollection-sidecar-interval)couchbaseclusters.spec.logging.audit.garbageCollection.sidecar.interval #### [](#constraints-133)Constraints **Type**: `string` **Default**: `20m` #### [](#description-133)Description The interval at which to check for rotated log files to remove, defaults to 20 minutes. ### [](#couchbaseclusters-spec-logging-audit-garbagecollection-sidecar-resources)couchbaseclusters.spec.logging.audit.garbageCollection.sidecar.resources #### [](#constraints-134)Constraints **Type**: `object` #### [](#description-134)Description Resources is the resource requirements for the cleanup container. Will be populated by Kubernetes defaults if not specified. ### [](#couchbaseclusters-spec-logging-audit-rotation)couchbaseclusters.spec.logging.audit.rotation #### [](#constraints-135)Constraints **Type**: `object` #### [](#description-135)Description The interval to optionally rotate the audit log. This is passed to the REST API, see here for details: . ### [](#couchbaseclusters-spec-logging-audit-rotation-interval)couchbaseclusters.spec.logging.audit.rotation.interval #### [](#constraints-136)Constraints **Type**: `string` **Default**: `15m` #### [](#description-136)Description The interval at which to rotate log files, defaults to 15 minutes. ### [](#couchbaseclusters-spec-logging-audit-rotation-pruneage)couchbaseclusters.spec.logging.audit.rotation.pruneAge #### [](#constraints-137)Constraints **Type**: `string` **Default**: `0` #### [](#description-137)Description How long Couchbase Server keeps rotated audit logs. If set to 0 (the default) then audit logs won't be pruned. Has a maximum of 35791394 seconds. ### [](#couchbaseclusters-spec-logging-audit-rotation-size)couchbaseclusters.spec.logging.audit.rotation.size #### [](#constraints-138)Constraints **Type**: `string` **Default**: `20Mi` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-138)Description Size allows the specification of a rotation size for the log, defaults to 20Mi. More info: . ### [](#couchbaseclusters-spec-logging-logretentioncount)couchbaseclusters.spec.logging.logRetentionCount #### [](#constraints-139)Constraints **Type**: `integer` **Minimum**: `0` #### [](#description-139)Description LogRetentionCount gives the number of persistent log PVCs to keep. ### [](#couchbaseclusters-spec-logging-logretentiontime)couchbaseclusters.spec.logging.logRetentionTime #### [](#constraints-140)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^\d+(ns|us|ms|s|m|h)$` #### [](#description-140)Description LogRetentionTime gives the time to keep persistent log PVCs alive for. ### [](#couchbaseclusters-spec-logging-server)couchbaseclusters.spec.logging.server #### [](#constraints-141)Constraints **Type**: `object` #### [](#description-141)Description Specification of all logging configuration required to manage the sidecar containers in each pod. ### [](#couchbaseclusters-spec-logging-server-configurationname)couchbaseclusters.spec.logging.server.configurationName #### [](#constraints-142)Constraints **Type**: `string` **Default**: `fluent-bit-config` #### [](#description-142)Description ConfigurationName is the name of the Secret to use holding the logging configuration in the namespace. A Secret is used to ensure we can safely store credentials but this can be populated from plaintext if acceptable too. If it does not exist then one will be created with defaults in the namespace so it can be easily updated whilst running. Note that if running multiple clusters in the same kubernetes namespace then you should use a separate Secret for each, otherwise the first cluster will take ownership (if created) and the Secret will be cleaned up when that cluster is removed. If running clusters in separate namespaces then they will be separate Secrets anyway. ### [](#couchbaseclusters-spec-logging-server-enabled)couchbaseclusters.spec.logging.server.enabled #### [](#constraints-143)Constraints **Type**: `boolean` #### [](#description-143)Description Enabled is a boolean that enables the logging sidecar container. ### [](#couchbaseclusters-spec-logging-server-manageconfiguration)couchbaseclusters.spec.logging.server.manageConfiguration #### [](#constraints-144)Constraints **Type**: `boolean` **Default**: `True` #### [](#description-144)Description A boolean which indicates whether the operator should manage the configuration or not. If omitted then this defaults to true which means the operator will attempt to reconcile it to default values. To use a custom configuration make sure to set this to false. Note that the ownership of any Secret is not changed so if a Secret is created externally it can be updated by the operator but it's ownership stays the same so it will be cleaned up when it's owner is. ### [](#couchbaseclusters-spec-logging-server-sidecar)couchbaseclusters.spec.logging.server.sidecar #### [](#constraints-145)Constraints **Type**: `object` **Default**: `{}` #### [](#description-145)Description Any specific logging sidecar container configuration. ### [](#couchbaseclusters-spec-logging-server-sidecar-configurationmountpath)couchbaseclusters.spec.logging.server.sidecar.configurationMountPath #### [](#constraints-146)Constraints **Type**: `string` **Default**: `/fluent-bit/config/` #### [](#description-146)Description ConfigurationMountPath is the location to mount the ConfigurationName Secret into the image. If another log shipping image is used that needs a different mount then modify this. Note that the configuration file must be called 'fluent-bit.conf' at the root of this path, there is no provision for overriding the name of the config file passed as the COUCHBASE\_LOGS\_CONFIG\_FILE environment variable. ### [](#couchbaseclusters-spec-logging-server-sidecar-image)couchbaseclusters.spec.logging.server.sidecar.image #### [](#constraints-147)Constraints **Type**: `string` **Default**: `couchbase/fluent-bit:1.2.1` #### [](#description-147)Description Image is the image to be used to deal with logging as a sidecar. No validation is carried out as this can be any arbitrary repo and tag. It will default to the latest supported version of Fluent Bit. ### [](#couchbaseclusters-spec-logging-server-sidecar-resources)couchbaseclusters.spec.logging.server.sidecar.resources #### [](#constraints-148)Constraints **Type**: `object` #### [](#description-148)Description Resources is the resource requirements for the sidecar container. Will be populated by Kubernetes defaults if not specified. ### [](#couchbaseclusters-spec-monitoring)couchbaseclusters.spec.monitoring #### [](#constraints-149)Constraints **Type**: `object` #### [](#description-149)Description **DEPRECATED** \- By Couchbase Server metrics endpoint on version 7.0+ Monitoring defines any Operator managed integration into 3rd party monitoring infrastructure. ### [](#couchbaseclusters-spec-monitoring-prometheus)couchbaseclusters.spec.monitoring.prometheus #### [](#constraints-150)Constraints **Type**: `object` #### [](#description-150)Description **DEPRECATED** \- By Couchbase Server metrics endpoint on version 7.0+ Prometheus provides integration with Prometheus monitoring. ### [](#couchbaseclusters-spec-monitoring-prometheus-authorizationsecret)couchbaseclusters.spec.monitoring.prometheus.authorizationSecret #### [](#constraints-151)Constraints **Type**: `string` #### [](#description-151)Description AuthorizationSecret is the name of a Kubernetes secret that contains a bearer token to authorize GET requests to the metrics endpoint. ### [](#couchbaseclusters-spec-monitoring-prometheus-enabled)couchbaseclusters.spec.monitoring.prometheus.enabled #### [](#constraints-152)Constraints **Type**: `boolean` #### [](#description-152)Description Enabled is a boolean that enables/disables the metrics sidecar container. This must be set to true, when image is provided. ### [](#couchbaseclusters-spec-monitoring-prometheus-image)couchbaseclusters.spec.monitoring.prometheus.image #### [](#constraints-153)Constraints **Required** **Type**: `string` #### [](#description-153)Description Image is the metrics image to be used to collect metrics. No validation is carried out as this can be any arbitrary repo and tag. enabled must be set to true, when image is provided. ### [](#couchbaseclusters-spec-monitoring-prometheus-refreshrate)couchbaseclusters.spec.monitoring.prometheus.refreshRate #### [](#constraints-154)Constraints **Type**: `integer` **Default**: `60` **Minimum**: `1` **Maximum**: `600` #### [](#description-154)Description RefreshRate is the frequency in which cached statistics are updated in seconds. Shorter intervals will add additional resource overhead to clusters running Couchbase Server 7.0+ Default is 60 seconds, Maximum value is 600 seconds, and minimum value is 1 second. ### [](#couchbaseclusters-spec-monitoring-prometheus-resources)couchbaseclusters.spec.monitoring.prometheus.resources #### [](#constraints-155)Constraints **Type**: `object` #### [](#description-155)Description Resources is the resource requirements for the metrics container. Will be populated by Kubernetes defaults if not specified. ### [](#couchbaseclusters-spec-networking)couchbaseclusters.spec.networking #### [](#constraints-156)Constraints **Type**: `object` #### [](#description-156)Description Networking defines Couchbase cluster networking options such as network topology, TLS and DDNS settings. ### [](#couchbaseclusters-spec-networking-addressfamily)couchbaseclusters.spec.networking.addressFamily #### [](#constraints-157)Constraints **Type**: `string` **Enumerations**: `IPv4, IPv6` #### [](#description-157)Description AddressFamily allows the manual selection of the address family to use. When this field is not set, Couchbase server will default to using IPv4 for internal communication and also support IPv6 on dual stack systems. Setting this field to either IPv4 or IPv6 will force Couchbase to use the selected protocol for internal communication, and also disable all other protocols to provide added security and simplicty when defining firewall rules. Disabling of address families is only supported in Couchbase Server 7.0.2+. ### [](#couchbaseclusters-spec-networking-adminconsoleservicetemplate)couchbaseclusters.spec.networking.adminConsoleServiceTemplate #### [](#constraints-158)Constraints **Type**: `object` #### [](#description-158)Description AdminConsoleServiceTemplate provides a template used by the Operator to create and manage the admin console service. This allows services to be annotated, the service type defined and any other options that Kubernetes provides. When using a LoadBalancer service type, TLS and dynamic DNS must also be enabled. The Operator reserves the right to modify or replace any field. More info: . ### [](#couchbaseclusters-spec-networking-adminconsoleservicetype)couchbaseclusters.spec.networking.adminConsoleServiceType #### [](#constraints-159)Constraints **Type**: `string` **Default**: `NodePort` **Enumerations**: `NodePort, LoadBalancer` #### [](#description-159)Description **DEPRECATED** \- by adminConsoleServiceTemplate. AdminConsoleServiceType defines whether to create a node port or load balancer service. When using a LoadBalancer service type, TLS and dynamic DNS must also be enabled. This field must be one of "NodePort" or "LoadBalancer", defaulting to "NodePort". ### [](#couchbaseclusters-spec-networking-adminconsoleservices)couchbaseclusters.spec.networking.adminConsoleServices #### [](#constraints-160)Constraints **Type**: `[]string` **Enumerations**: `admin, data, index, query, search, eventing, analytics` #### [](#description-160)Description **DEPRECATED** \- not required by Couchbase Server. AdminConsoleServices is a selector to choose specific services to expose via the admin console. This field may contain any of "data", "index", "query", "search", "eventing" and "analytics". Each service may only be included once. ### [](#couchbaseclusters-spec-networking-cloudnativegateway)couchbaseclusters.spec.networking.cloudNativeGateway #### [](#constraints-161)Constraints **Type**: `object` #### [](#description-161)Description CloudNativeGateway is used to provision a gRPC gateway proxying a Couchbase cluster. ### [](#couchbaseclusters-spec-networking-cloudnativegateway-image)couchbaseclusters.spec.networking.cloudNativeGateway.image #### [](#constraints-162)Constraints **Required** **Type**: `string` #### [](#description-162)Description Image is the Cloud Native Gateway image to be used to run the sidecar container. No validation is carried out as this can be any arbitrary repo and tag. TODO: provide a default kubebuilder default image tag as field is mandatory. ### [](#couchbaseclusters-spec-networking-cloudnativegateway-loglevel)couchbaseclusters.spec.networking.cloudNativeGateway.logLevel #### [](#constraints-163)Constraints **Required** **Type**: `string` **Default**: `info` **Enumerations**: `fatal, panic, dpanic, error, warn, info, debug` #### [](#description-163)Description **DEVELOPER PREVIEW** \- This feature is in developer preview. LogLevel controls the verbosity of cloud native logs. This field must be one of "fatal", "panic", "dpanic", "error", "warn", "info", "debug" defaulting to "info". ### [](#couchbaseclusters-spec-networking-cloudnativegateway-terminationgraceperiodseconds)couchbaseclusters.spec.networking.cloudNativeGateway.terminationGracePeriodSeconds #### [](#constraints-164)Constraints **Type**: `integer` **Default**: `75` #### [](#description-164)Description TerminationGracePeriodSeconds specifies the grace period for the container to terminate. Defaults to 75 seconds. ### [](#couchbaseclusters-spec-networking-cloudnativegateway-tls)couchbaseclusters.spec.networking.cloudNativeGateway.tls #### [](#constraints-165)Constraints **Type**: `object` #### [](#description-165)Description TLS defines the TLS configuration for the Cloud Native Gateway server including server and client certificate configuration, and TLS security policies. If no TLS config are explicitly provided, the operator generates/manages self-signed certs/keys and creates a k8s secret named `couchbase-cloud-native-gateway-self-signed-secret-`unique to a Couchbase cluster, which is volume mounted to the cb k8s pod. This action could be overidden at the outset or later, by using the below TLS config or generating the secret of same name as `couchbase-cloud-native-gateway-self-signed-secret-` with certificates conforming to the keys of well-known type "kubernetes.io/tls" with "tls.crt" and "tls.key". N.B. The secret is on per cluster basis so it's advised to use the unique cluster name else would be ignored. ### [](#couchbaseclusters-spec-networking-cloudnativegateway-tls-serversecretname)couchbaseclusters.spec.networking.cloudNativeGateway.tls.serverSecretName #### [](#constraints-166)Constraints **Type**: `string` #### [](#description-166)Description ServerSecretName specifies the secret name, in the same namespace as the cluster, that contains Cloud Native Gateway gRPC server TLS data. The secret is expected to contain "tls.crt" and "tls.key" as per the kubernetes.io/tls secret type. ### [](#couchbaseclusters-spec-networking-disableuioverhttp)couchbaseclusters.spec.networking.disableUIOverHTTP #### [](#constraints-167)Constraints **Type**: `boolean` #### [](#description-167)Description DisableUIOverHTTP is used to explicitly enable and disable UI access over the HTTP protocol. If not specified, this field defaults to false. ### [](#couchbaseclusters-spec-networking-disableuioverhttps)couchbaseclusters.spec.networking.disableUIOverHTTPS #### [](#constraints-168)Constraints **Type**: `boolean` #### [](#description-168)Description DisableUIOverHTTPS is used to explicitly enable and disable UI access over the HTTPS protocol. If not specified, this field defaults to false. ### [](#couchbaseclusters-spec-networking-dns)couchbaseclusters.spec.networking.dns #### [](#constraints-169)Constraints **Type**: `object` #### [](#description-169)Description DNS defines information required for Dynamic DNS support. ### [](#couchbaseclusters-spec-networking-dns-domain)couchbaseclusters.spec.networking.dns.domain #### [](#constraints-170)Constraints **Type**: `string` #### [](#description-170)Description Domain is the domain to create pods in. When populated the Operator will annotate the admin console and per-pod services with the key "external-dns.alpha.kubernetes.io/hostname". These annotations can be used directly by a Kubernetes External-DNS controller to replicate load balancer service IP addresses into a public DNS server. ### [](#couchbaseclusters-spec-networking-exposeadminconsole)couchbaseclusters.spec.networking.exposeAdminConsole #### [](#constraints-171)Constraints **Type**: `boolean` #### [](#description-171)Description ExposeAdminConsole creates a service referencing the admin console. The service is configured by the adminConsoleServiceTemplate field. ### [](#couchbaseclusters-spec-networking-exposedfeatureservicetemplate)couchbaseclusters.spec.networking.exposedFeatureServiceTemplate #### [](#constraints-172)Constraints **Type**: `object` #### [](#description-172)Description ExposedFeatureServiceTemplate provides a template used by the Operator to create and manage per-pod services. This allows services to be annotated, the service type defined and any other options that Kubernetes provides. When using a LoadBalancer service type, TLS and dynamic DNS must also be enabled. The Operator reserves the right to modify or replace any field. More info: . ### [](#couchbaseclusters-spec-networking-exposedfeatureservicetype)couchbaseclusters.spec.networking.exposedFeatureServiceType #### [](#constraints-173)Constraints **Type**: `string` **Default**: `NodePort` **Enumerations**: `NodePort, LoadBalancer` #### [](#description-173)Description **DEPRECATED** \- by exposedFeatureServiceTemplate. ExposedFeatureServiceType defines whether to create a node port or load balancer service. When using a LoadBalancer service type, TLS and dynamic DNS must also be enabled. This field must be one of "NodePort" or "LoadBalancer", defaulting to "NodePort". ### [](#couchbaseclusters-spec-networking-exposedfeaturetrafficpolicy)couchbaseclusters.spec.networking.exposedFeatureTrafficPolicy #### [](#constraints-174)Constraints **Type**: `string` **Enumerations**: `Cluster, Local` #### [](#description-174)Description **DEPRECATED** \- by exposedFeatureServiceTemplate. ExposedFeatureTrafficPolicy defines how packets should be routed from a load balancer service to a Couchbase pod. When local, traffic is routed directly to the pod. When cluster, traffic is routed to any node, then forwarded on. While cluster routing may be slower, there are some situations where it is required for connectivity. This field must be either "Cluster" or "Local", defaulting to "Local",. ### [](#couchbaseclusters-spec-networking-exposedfeatures)couchbaseclusters.spec.networking.exposedFeatures #### [](#constraints-175)Constraints **Type**: `[]string` **Enumerations**: `admin, xdcr, client, backup` #### [](#description-175)Description ExposedFeatures is a list of Couchbase features to expose when using a networking model that exposes the Couchbase cluster externally to Kubernetes. This field also triggers the creation of per-pod services used by clients to connect to the Couchbase cluster. When admin, only the administrator port is exposed, allowing remote administration. When xdcr, only the services required for remote replication are exposed. The xdcr feature is only required when the cluster is the destination of an XDCR replication. When client, all services are exposed as required for client SDK operation. This field may contain any of "admin", "xdcr" and "client". Each feature may only be included once. ### [](#couchbaseclusters-spec-networking-loadbalancersourceranges)couchbaseclusters.spec.networking.loadBalancerSourceRanges #### [](#constraints-176)Constraints **Type**: `[]string` **Pattern (Regular Expression)**: `^\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/\d{1,2}$` #### [](#description-176)Description **DEPRECATED** \- by adminConsoleServiceTemplate and exposedFeatureServiceTemplate. LoadBalancerSourceRanges applies only when an exposed service is of type LoadBalancer and limits the source IP ranges that are allowed to use the service. Items must use IPv4 class-less interdomain routing (CIDR) notation e.g. 10.0.0.0/16. ### [](#couchbaseclusters-spec-networking-networkplatform)couchbaseclusters.spec.networking.networkPlatform #### [](#constraints-177)Constraints **Type**: `string` **Enumerations**: `Istio` #### [](#description-177)Description NetworkPlatform is used to enable support for various networking technologies. This field must be one of "Istio". ### [](#couchbaseclusters-spec-networking-serviceannotations)couchbaseclusters.spec.networking.serviceAnnotations #### [](#constraints-178)Constraints **Type**: `map[string]string` #### [](#description-178)Description **DEPRECATED** \- by adminConsoleServiceTemplate and exposedFeatureServiceTemplate. ServiceAnnotations allows services to be annotated with custom labels. Operator annotations are merged on top of these so have precedence as they are required for correct operation. ### [](#couchbaseclusters-spec-networking-tls)couchbaseclusters.spec.networking.tls #### [](#constraints-179)Constraints **Type**: `object` #### [](#description-179)Description TLS defines the TLS configuration for the cluster including server and client certificate configuration, and TLS security policies. ### [](#couchbaseclusters-spec-networking-tls-allowplaintextcertreload)couchbaseclusters.spec.networking.tls.allowPlainTextCertReload #### [](#constraints-180)Constraints **Type**: `boolean` **Default**: `False` #### [](#description-180)Description AllowPlainTextCertReload allows the reload of TLS certificates in plain text. This option should only be enabled as a means to recover connectivity with server in the event that any of the server certificates expire. When enabled the Operator only attempts plain text cert reloading when expired certificates are detected. ### [](#couchbaseclusters-spec-networking-tls-ciphersuites)couchbaseclusters.spec.networking.tls.cipherSuites #### [](#constraints-181)Constraints **Type**: `[]string` #### [](#description-181)Description CipherSuites specifies a list of cipher suites for Couchbase server to select from when negotiating TLS handshakes with a client. Suites are not validated by the Operator. Run "openssl ciphers -v" in a Couchbase server pod to interrogate supported values. ### [](#couchbaseclusters-spec-networking-tls-clientcertificatepaths)couchbaseclusters.spec.networking.tls.clientCertificatePaths #### [](#constraints-182)Constraints **Type**: `[]object` #### [](#description-182)Description ClientCertificatePaths defines where to look in client certificates in order to extract the user name. ### [](#couchbaseclusters-spec-networking-tls-clientcertificatepaths-delimiter)couchbaseclusters.spec.networking.tls.clientCertificatePaths.delimiter #### [](#constraints-183)Constraints **Type**: `string` #### [](#description-183)Description Delimiter if specified allows a suffix to be stripped from the username, once extracted from the certificate path. ### [](#couchbaseclusters-spec-networking-tls-clientcertificatepaths-path)couchbaseclusters.spec.networking.tls.clientCertificatePaths.path #### [](#constraints-184)Constraints **Required** **Type**: `string` **Pattern (Regular Expression)**: `^subject\.cn|san\.uri|san\.dnsname|san\.email$` #### [](#description-184)Description Path defines where in the X.509 specification to extract the username from. This field must be either "subject.cn", "san.uri", "san.dnsname" or "san.email". ### [](#couchbaseclusters-spec-networking-tls-clientcertificatepaths-prefix)couchbaseclusters.spec.networking.tls.clientCertificatePaths.prefix #### [](#constraints-185)Constraints **Type**: `string` #### [](#description-185)Description Prefix allows a prefix to be stripped from the username, once extracted from the certificate path. ### [](#couchbaseclusters-spec-networking-tls-clientcertificatepolicy)couchbaseclusters.spec.networking.tls.clientCertificatePolicy #### [](#constraints-186)Constraints **Type**: `string` **Enumerations**: `enable, mandatory` #### [](#description-186)Description ClientCertificatePolicy defines the client authentication policy to use. If set, the Operator expects TLS configuration to contain a valid certificate/key pair for the Administrator account. ### [](#couchbaseclusters-spec-networking-tls-nodetonodeencryption)couchbaseclusters.spec.networking.tls.nodeToNodeEncryption #### [](#constraints-187)Constraints **Type**: `string` **Enumerations**: `ControlPlaneOnly, All, Strict` #### [](#description-187)Description NodeToNodeEncryption specifies whether to encrypt data between Couchbase nodes within the same cluster. This may come at the expense of performance. When control plane only encryption is used, only cluster management traffic is encrypted between nodes. When all, all traffic is encrypted, including database documents. When strict mode is used, it is the same as all, but also disables all plaintext ports. Strict mode is only available on Couchbase Server versions 7.1 and greater. Node to node encryption can only be used when TLS certificates are managed by the Operator. This field must be either "ControlPlaneOnly", "All", or "Strict". ### [](#couchbaseclusters-spec-networking-tls-passphrase)couchbaseclusters.spec.networking.tls.passphrase #### [](#constraints-188)Constraints **Type**: `object` #### [](#description-188)Description PassphraseConfig configures the passphrase key to use with encrypted certificates. The passphrase may be registered with Couchbase Server using a local script or a rest endpoint. Private key encryption is only available on Couchbase Server versions 7.1 and greater. ### [](#couchbaseclusters-spec-networking-tls-passphrase-rest)couchbaseclusters.spec.networking.tls.passphrase.rest #### [](#constraints-189)Constraints **Type**: `object` #### [](#description-189)Description PassphraseRestConfig is the configuration to register a private key passphrase with a rest endpoint. When the private key is accessed, Couchbase Server attempts to extract the password by means of the specified endpoint. The response status must be 200 and the response text must be the exact passphrase excluding newlines and extraneous spaces. ### [](#couchbaseclusters-spec-networking-tls-passphrase-rest-addressfamily)couchbaseclusters.spec.networking.tls.passphrase.rest.addressFamily #### [](#constraints-190)Constraints **Type**: `string` **Default**: `inet` **Enumerations**: `inet, inet6` #### [](#description-190)Description AddressFamily is the address family to use. By default inet (meaning IPV4) is used. ### [](#couchbaseclusters-spec-networking-tls-passphrase-rest-headers)couchbaseclusters.spec.networking.tls.passphrase.rest.headers #### [](#constraints-191)Constraints **Type**: `map[string]string` #### [](#description-191)Description Headers is a map of one or more key-value pairs to pass alongside the Get request. ### [](#couchbaseclusters-spec-networking-tls-passphrase-rest-timeout)couchbaseclusters.spec.networking.tls.passphrase.rest.timeout #### [](#constraints-192)Constraints **Type**: `integer` **Default**: `5000` #### [](#description-192)Description Timeout is the number of milliseconds that must elapse before the call is timed out. ### [](#couchbaseclusters-spec-networking-tls-passphrase-rest-url)couchbaseclusters.spec.networking.tls.passphrase.rest.url #### [](#constraints-193)Constraints **Required** **Type**: `string` #### [](#description-193)Description URL is the endpoint to be called to retrieve the passphrase. URL will be called using the GET method and may use http/https protocol. ### [](#couchbaseclusters-spec-networking-tls-passphrase-rest-verifypeer)couchbaseclusters.spec.networking.tls.passphrase.rest.verifyPeer #### [](#constraints-194)Constraints **Type**: `boolean` **Default**: `True` #### [](#description-194)Description VerifyPeer ensures peer verification is performed when Https is used. ### [](#couchbaseclusters-spec-networking-tls-passphrase-script)couchbaseclusters.spec.networking.tls.passphrase.script #### [](#constraints-195)Constraints **Type**: `object` #### [](#description-195)Description PassphraseScriptConfig is the configuration to register a private key passphrase with a script. The Operator auto-provisions the underlying script so this config simply provides a mechanism to perform the decryption of the Couchbase Private Key using a local script. ### [](#couchbaseclusters-spec-networking-tls-passphrase-script-secret)couchbaseclusters.spec.networking.tls.passphrase.script.secret #### [](#constraints-196)Constraints **Required** **Type**: `string` #### [](#description-196)Description Secret is the secret containing the passphrase string. The secret is expected to contain "passphrase" key with the passphrase string as a value. ### [](#couchbaseclusters-spec-networking-tls-rootcas)couchbaseclusters.spec.networking.tls.rootCAs #### [](#constraints-197)Constraints **Type**: `[]string` #### [](#description-197)Description RootCAs defines a set of secrets that reside in this namespace that contain additional CA certificates that should be installed in Couchbase. The CA certificates that are defined here are in addition to those defined for the cluster, optionally by couchbaseclusters.spec.networking.tls.secretSource, and thus should not be duplicated. Each Secret referred to must be of well-known type "kubernetes.io/tls" and must contain one or more CA certificates under the key "tls.crt". Multiple root CA certificates are only supported on Couchbase Server 7.1 and greater, and not with legacy couchbaseclusters.spec.networking.tls.static configuration. ### [](#couchbaseclusters-spec-networking-tls-secretsource)couchbaseclusters.spec.networking.tls.secretSource #### [](#constraints-198)Constraints **Type**: `object` #### [](#description-198)Description SecretSource enables the user to specify a secret conforming to the Kubernetes TLS secret specification that is used for the Couchbase server certificate, and optionally the Operator's client certificate, providing cert-manager compatibility without having to specify a separate root CA. A server CA certificate must be supplied by one of the provided methods. Certificates referred to must conform to the keys of well-known type "kubernetes.io/tls" with "tls.crt" and "tls.key". If the "tls.key" is an encrypted private key then the secret type can be the generic Opaque type since "kubernetes.io/tls" type secrets cannot verify encrypted keys. ### [](#couchbaseclusters-spec-networking-tls-secretsource-clientsecretname)couchbaseclusters.spec.networking.tls.secretSource.clientSecretName #### [](#constraints-199)Constraints **Type**: `string` #### [](#description-199)Description ClientSecretName specifies the secret name, in the same namespace as the cluster, the contains client TLS data. The secret is expected to contain "tls.crt" and "tls.key" as per the Kubernetes.io/tls secret type. ### [](#couchbaseclusters-spec-networking-tls-secretsource-serversecretname)couchbaseclusters.spec.networking.tls.secretSource.serverSecretName #### [](#constraints-200)Constraints **Required** **Type**: `string` #### [](#description-200)Description ServerSecretName specifies the secret name, in the same namespace as the cluster, that contains server TLS data. The secret is expected to contain "tls.crt" and "tls.key" as per the kubernetes.io/tls secret type. It may also contain "ca.crt". Only a single PEM formated x509 certificate can be provided to "ca.crt". The single certificate may also bundle together multiple root CA certificates. Multiple root CA certificates are only supported on Couchbase Server 7.1 and greater. ### [](#couchbaseclusters-spec-networking-tls-static)couchbaseclusters.spec.networking.tls.static #### [](#constraints-201)Constraints **Type**: `object` #### [](#description-201)Description **DEPRECATED** \- by couchbaseclusters.spec.networking.tls.secretSource. Static enables user to generate static x509 certificates and keys, put them into Kubernetes secrets, and specify them here. Static secrets are Couchbase specific, and follow no well-known standards. ### [](#couchbaseclusters-spec-networking-tls-static-operatorsecret)couchbaseclusters.spec.networking.tls.static.operatorSecret #### [](#constraints-202)Constraints **Type**: `string` #### [](#description-202)Description OperatorSecret is a secret name containing TLS certs used by operator to talk securely to this cluster. The secret must contain a CA certificate (data key ca.crt). If client authentication is enabled, then the secret must also contain a client certificate chain (data key "couchbase-operator.crt") and private key (data key "couchbase-operator.key"). ### [](#couchbaseclusters-spec-networking-tls-static-serversecret)couchbaseclusters.spec.networking.tls.static.serverSecret #### [](#constraints-203)Constraints **Type**: `string` #### [](#description-203)Description ServerSecret is a secret name containing TLS certs used by each Couchbase member pod for the communication between Couchbase server and its clients. The secret must contain a certificate chain (data key "chain.pem") and a private key (data key "pkey.key"). The private key must be in the PKCS#1 RSA format. The certificate chain must have a required set of X.509v3 subject alternative names for all cluster addressing modes. See the Operator TLS documentation for more information. ### [](#couchbaseclusters-spec-networking-tls-tlsminimumversion)couchbaseclusters.spec.networking.tls.tlsMinimumVersion #### [](#constraints-204)Constraints **Type**: `string` **Default**: `TLS1.2` **Enumerations**: `TLS1.0, TLS1.1, TLS1.2, TLS1.3` #### [](#description-204)Description TLSMinimumVersion specifies the minimum TLS version the Couchbase server can negotiate with a client. Must be one of TLS1.0, TLS1.1 TLS1.2 or TLS1.3, defaulting to TLS1.2\. TLS1.3 is only valid for Couchbase Server 7.1.0 onward. TLS1.0 and TLS1.1 are not valid for Couchbase Server 7.6.0 onward. ### [](#couchbaseclusters-spec-networking-waitforaddressreachable)couchbaseclusters.spec.networking.waitForAddressReachable #### [](#constraints-205)Constraints **Type**: `string` **Default**: `10m` #### [](#description-205)Description WaitForAddressReachable is used to set the timeout between when polling of external addresses is started, and when it is deemed a failure. Polling of DNS name availability inherently dangerous due to negative caching, so prefer the use of an initial `waitForAddressReachableDelay` to allow propagation. ### [](#couchbaseclusters-spec-networking-waitforaddressreachabledelay)couchbaseclusters.spec.networking.waitForAddressReachableDelay #### [](#constraints-206)Constraints **Type**: `string` **Default**: `2m` #### [](#description-206)Description WaitForAddressReachableDelay is used to defer operator checks that ensure external addresses are reachable before new nodes are balanced in to the cluster. This prevents negative DNS caching while waiting for external-DDNS controllers to propagate addresses. ### [](#couchbaseclusters-spec-onlinevolumeexpansiontimeoutinmins)couchbaseclusters.spec.onlineVolumeExpansionTimeoutInMins #### [](#constraints-207)Constraints **Type**: `integer` **Minimum**: `0` **Maximum**: `30` #### [](#description-207)Description OnlineVolumeExpansionTimeoutInMins must be provided as a retry mechanism with a timeout in minutes for expanding volumes. This must only be provided, if EnableOnlineVolumeExpansion is set to true. Value must be between 0 and 30\. If no value is provided, then it defaults to 10 minutes. ### [](#couchbaseclusters-spec-paused)couchbaseclusters.spec.paused #### [](#constraints-208)Constraints **Type**: `boolean` #### [](#description-208)Description Paused is to pause the control of the operator for the Couchbase cluster. This does not pause the cluster itself, instead stopping the operator from taking any action. ### [](#couchbaseclusters-spec-platform)couchbaseclusters.spec.platform #### [](#constraints-209)Constraints **Type**: `string` **Enumerations**: `aws, gce, azure` #### [](#description-209)Description Platform gives a hint as to what platform we are running on and how to configure services. This field must be one of "aws", "gke" or "azure". ### [](#couchbaseclusters-spec-recoverypolicy)couchbaseclusters.spec.recoveryPolicy #### [](#constraints-210)Constraints **Type**: `string` **Enumerations**: `PrioritizeDataIntegrity, PrioritizeUptime` #### [](#description-210)Description RecoveryPolicy controls how aggressive the Operator is when recovering cluster topology. When PrioritizeDataIntegrity, the Operator will delegate failover exclusively to Couchbase server, relying on it to only allow recovery when safe to do so. When PrioritizeUptime, the Operator will wait for a period after the expected auto-failover of the cluster, before forcefully failing-over the pods. This may cause data loss, and is only expected to be used on clusters with ephemeral data, where the loss of the pod means that the data is known to be unrecoverable. This field must be either "PrioritizeDataIntegrity" or "PrioritizeUptime", defaulting to "PrioritizeDataIntegrity". ### [](#couchbaseclusters-spec-rollingupgrade)couchbaseclusters.spec.rollingUpgrade #### [](#constraints-211)Constraints **Type**: `object` #### [](#description-211)Description When `spec.upgradeStrategy` is set to `RollingUpgrade` it will, by default, upgrade one pod at a time. If this field is specified then that number can be increased. ### [](#couchbaseclusters-spec-rollingupgrade-maxupgradable)couchbaseclusters.spec.rollingUpgrade.maxUpgradable #### [](#constraints-212)Constraints **Type**: `integer` **Minimum**: `1` #### [](#description-212)Description MaxUpgradable allows the number of pods affected by an upgrade at any one time to be increased. By default a rolling upgrade will upgrade one pod at a time. This field allows that limit to be removed. This field must be greater than zero. The smallest of `maxUpgradable` and `maxUpgradablePercent` takes precedence if both are defined. ### [](#couchbaseclusters-spec-rollingupgrade-maxupgradablepercent)couchbaseclusters.spec.rollingUpgrade.maxUpgradablePercent #### [](#constraints-213)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(100|[1-9][0-9]|[1-9])%$` #### [](#description-213)Description MaxUpgradablePercent allows the number of pods affected by an upgrade at any one time to be increased. By default a rolling upgrade will upgrade one pod at a time. This field allows that limit to be removed. This field must be an integer percentage, e.g. "10%", in the range 1% to 100%. Percentages are relative to the total cluster size, and rounded down to the nearest whole number, with a minimum of 1\. For example, a 10 pod cluster, and 25% allowed to upgrade, would yield 2.5 pods per iteration, rounded down to 2\. The smallest of `maxUpgradable` and `maxUpgradablePercent` takes precedence if both are defined. ### [](#couchbaseclusters-spec-security)couchbaseclusters.spec.security #### [](#constraints-214)Constraints **Required** **Type**: `object` #### [](#description-214)Description Security defines Couchbase cluster security options such as the administrator account username and password, and user RBAC settings. ### [](#couchbaseclusters-spec-security-adminsecret)couchbaseclusters.spec.security.adminSecret #### [](#constraints-215)Constraints **Required** **Type**: `string` #### [](#description-215)Description AdminSecret is the name of a Kubernetes secret to use for administrator authentication. The admin secret must contain the keys "username" and "password". The password data must be at least 6 characters in length, and not contain the any of the characters `()<>,;:\"/[]?={}`. ### [](#couchbaseclusters-spec-security-ldap)couchbaseclusters.spec.security.ldap #### [](#constraints-216)Constraints **Type**: `object` #### [](#description-216)Description LDAP provides settings to authenticate and authorize LDAP users with Couchbase Server. When specified, the Operator keeps these settings in sync with Cocuhbase Server's LDAP configuration. Leave empty to manually manage LDAP configuration. ### [](#couchbaseclusters-spec-security-ldap-authenticationenabled)couchbaseclusters.spec.security.ldap.authenticationEnabled #### [](#constraints-217)Constraints **Type**: `boolean` **Default**: `True` #### [](#description-217)Description AuthenticationEnabled allows users who attempt to access Couchbase Server without having been added as local users to be authenticated against the specified LDAP Host(s). ### [](#couchbaseclusters-spec-security-ldap-authorizationenabled)couchbaseclusters.spec.security.ldap.authorizationEnabled #### [](#constraints-218)Constraints **Type**: `boolean` #### [](#description-218)Description AuthorizationEnabled allows authenticated LDAP users to be authorized with RBAC roles granted to any Couchbase Server group associated with the user. ### [](#couchbaseclusters-spec-security-ldap-binddn)couchbaseclusters.spec.security.ldap.bindDN #### [](#constraints-219)Constraints **Type**: `string` #### [](#description-219)Description DN to use for searching users and groups synchronization. More info: . ### [](#couchbaseclusters-spec-security-ldap-bindsecret)couchbaseclusters.spec.security.ldap.bindSecret #### [](#constraints-220)Constraints **Required** **Type**: `string` #### [](#description-220)Description BindSecret is the name of a Kubernetes secret to use containing password for LDAP user binding. The bindSecret must have a key with the name "password" and a value which corresponds to the password of the binding LDAP user. ### [](#couchbaseclusters-spec-security-ldap-cacert)couchbaseclusters.spec.security.ldap.cacert #### [](#constraints-221)Constraints **Type**: `string` #### [](#description-221)Description **DEPRECATED** \- Field is ignored, use tlsSecret. CA Certificate in PEM format to be used in LDAP server certificate validation. This cert is the string form of the secret provided to `spec.tls.tlsSecret`. ### [](#couchbaseclusters-spec-security-ldap-cachevaluelifetime)couchbaseclusters.spec.security.ldap.cacheValueLifetime #### [](#constraints-222)Constraints **Type**: `integer` **Default**: `30000` #### [](#description-222)Description Lifetime of values in cache in milliseconds. Default 300000 ms. More info: . ### [](#couchbaseclusters-spec-security-ldap-encryption)couchbaseclusters.spec.security.ldap.encryption #### [](#constraints-223)Constraints **Type**: `string` **Enumerations**: `None, StartTLSExtension, TLS` #### [](#description-223)Description Encryption determines how the connection with the LDAP server should be encrypted. Encryption may set as either StartTLSExtension, TLS, or false. When set to "false" then no verification of the LDAP hostname is performed. When Encryption is StartTLSExtension, or TLS is set then the default behavior is to use the certificate already loaded into the Couchbase Cluster for certificate validation, otherwise `ldap.tlsSecret` may be set to override The Couchbase certificate. ### [](#couchbaseclusters-spec-security-ldap-groupsquery)couchbaseclusters.spec.security.ldap.groupsQuery #### [](#constraints-224)Constraints **Type**: `string` #### [](#description-224)Description LDAP query, to get the users' groups by username in RFC4516 format. More info: . ### [](#couchbaseclusters-spec-security-ldap-hosts)couchbaseclusters.spec.security.ldap.hosts #### [](#constraints-225)Constraints **Required** **Type**: `[]string` **Minimum Items**: `1` #### [](#description-225)Description List of LDAP hosts to provide authentication-support for Couchbase Server. Host name must be a valid IP address or DNS Name e.g openldap.default.svc, 10.0.92.147. ### [](#couchbaseclusters-spec-security-ldap-middleboxcompmode)couchbaseclusters.spec.security.ldap.middleboxCompMode #### [](#constraints-226)Constraints **Type**: `boolean` **Default**: `True` #### [](#description-226)Description Sets middlebox compatibility mode for LDAP. This option is only available on Couchbase Server 7.6.0+. ### [](#couchbaseclusters-spec-security-ldap-nestedgroupsenabled)couchbaseclusters.spec.security.ldap.nestedGroupsEnabled #### [](#constraints-227)Constraints **Type**: `boolean` #### [](#description-227)Description If enabled Couchbase server will try to recursively search for groups for every discovered ldap group. groups\_query will be user for the search. More info: . ### [](#couchbaseclusters-spec-security-ldap-nestedgroupsmaxdepth)couchbaseclusters.spec.security.ldap.nestedGroupsMaxDepth #### [](#constraints-228)Constraints **Type**: `integer` **Default**: `10` **Minimum**: `1` **Maximum**: `100` #### [](#description-228)Description Maximum number of recursive groups requests the server is allowed to perform. Requires NestedGroupsEnabled. Values between 1 and 100: the default is 10\. More info: . ### [](#couchbaseclusters-spec-security-ldap-port)couchbaseclusters.spec.security.ldap.port #### [](#constraints-229)Constraints **Required** **Type**: `integer` **Default**: `389` #### [](#description-229)Description LDAP port. This is typically 389 for LDAP, and 636 for LDAPS. ### [](#couchbaseclusters-spec-security-ldap-servercertvalidation)couchbaseclusters.spec.security.ldap.serverCertValidation #### [](#constraints-230)Constraints **Type**: `boolean` #### [](#description-230)Description Whether server certificate validation be enabled. ### [](#couchbaseclusters-spec-security-ldap-tlssecret)couchbaseclusters.spec.security.ldap.tlsSecret #### [](#constraints-231)Constraints **Type**: `string` #### [](#description-231)Description TLSSecret is the name of a Kubernetes secret to use explcitly for LDAP ca cert. If TLSSecret is not provided, certificates found in `couchbaseclusters.spec.networking.tls.rootCAs`will be used instead. If provided, the secret must contain the ca to be used under the name "ca.crt". ### [](#couchbaseclusters-spec-security-ldap-userdnmapping)couchbaseclusters.spec.security.ldap.userDNMapping #### [](#constraints-232)Constraints **Type**: `object` #### [](#description-232)Description User to distinguished name (DN) mapping. If none is specified, the username is used as the user's distinguished name. More info: . ### [](#couchbaseclusters-spec-security-ldap-userdnmapping-query)couchbaseclusters.spec.security.ldap.userDNMapping.query #### [](#constraints-233)Constraints **Type**: `string` #### [](#description-233)Description Query is the LDAP query to run to map from Couchbase user to LDAP distinguished name. ### [](#couchbaseclusters-spec-security-ldap-userdnmapping-template)couchbaseclusters.spec.security.ldap.userDNMapping.template #### [](#constraints-234)Constraints **Type**: `string` #### [](#description-234)Description This field specifies list of templates to use for providing username to DN mapping. The template may contain a placeholder specified as `%u` to represent the Couchbase user who is attempting to gain access. ### [](#couchbaseclusters-spec-security-podsecuritycontext)couchbaseclusters.spec.security.podSecurityContext #### [](#constraints-235)Constraints **Type**: `object` #### [](#description-235)Description PodSecurityContext allows the configuration of the security context for all Couchbase server pods. When using persistent volumes you may need to set the fsGroup field in order to write to the volume. For non-root clusters you must also set runAsUser to 1000, corresponding to the Couchbase user in official container images. More info: . ### [](#couchbaseclusters-spec-security-podsecuritycontext-fsgroup)couchbaseclusters.spec.security.podSecurityContext.fsGroup #### [](#constraints-236)Constraints **Type**: `integer` #### [](#description-236)Description A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to change the ownership of that volume to be owned by the pod: 1\. The owning GID will be the FSGroup 2\. The setgid bit is set (new files created in the volume will be owned by FSGroup) 3\. The permission bits are OR'd with rw-rw---- If unset, the Kubelet will not modify the ownership and permissions of any volume. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-podsecuritycontext-fsgroupchangepolicy)couchbaseclusters.spec.security.podSecurityContext.fsGroupChangePolicy #### [](#constraints-237)Constraints **Type**: `string` #### [](#description-237)Description fsGroupChangePolicy defines behavior of changing ownership and permission of the volume before being exposed inside Pod. This field will only apply to volume types which support fsGroup based ownership(and permissions). It will have no effect on ephemeral volume types such as: secret, configmaps and emptydir. Valid values are "OnRootMismatch" and "Always". If not specified, "Always" is used. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-podsecuritycontext-runasgroup)couchbaseclusters.spec.security.podSecurityContext.runAsGroup #### [](#constraints-238)Constraints **Type**: `integer` #### [](#description-238)Description The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-podsecuritycontext-runasnonroot)couchbaseclusters.spec.security.podSecurityContext.runAsNonRoot #### [](#constraints-239)Constraints **Type**: `boolean` #### [](#description-239)Description Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. ### [](#couchbaseclusters-spec-security-podsecuritycontext-runasuser)couchbaseclusters.spec.security.podSecurityContext.runAsUser #### [](#constraints-240)Constraints **Type**: `integer` #### [](#description-240)Description The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-podsecuritycontext-selinuxoptions)couchbaseclusters.spec.security.podSecurityContext.seLinuxOptions #### [](#constraints-241)Constraints **Type**: `object` #### [](#description-241)Description The SELinux context to be applied to all containers. If unspecified, the container runtime will allocate a random SELinux context for each container. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-podsecuritycontext-selinuxoptions-level)couchbaseclusters.spec.security.podSecurityContext.seLinuxOptions.level #### [](#constraints-242)Constraints **Type**: `string` #### [](#description-242)Description Level is SELinux level label that applies to the container. ### [](#couchbaseclusters-spec-security-podsecuritycontext-selinuxoptions-role)couchbaseclusters.spec.security.podSecurityContext.seLinuxOptions.role #### [](#constraints-243)Constraints **Type**: `string` #### [](#description-243)Description Role is a SELinux role label that applies to the container. ### [](#couchbaseclusters-spec-security-podsecuritycontext-selinuxoptions-type)couchbaseclusters.spec.security.podSecurityContext.seLinuxOptions.type #### [](#constraints-244)Constraints **Type**: `string` #### [](#description-244)Description Type is a SELinux type label that applies to the container. ### [](#couchbaseclusters-spec-security-podsecuritycontext-selinuxoptions-user)couchbaseclusters.spec.security.podSecurityContext.seLinuxOptions.user #### [](#constraints-245)Constraints **Type**: `string` #### [](#description-245)Description User is a SELinux user label that applies to the container. ### [](#couchbaseclusters-spec-security-podsecuritycontext-seccompprofile)couchbaseclusters.spec.security.podSecurityContext.seccompProfile #### [](#constraints-246)Constraints **Type**: `object` #### [](#description-246)Description The seccomp options to use by the containers in this pod. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-podsecuritycontext-seccompprofile-localhostprofile)couchbaseclusters.spec.security.podSecurityContext.seccompProfile.localhostProfile #### [](#constraints-247)Constraints **Type**: `string` #### [](#description-247)Description localhostProfile indicates a profile defined in a file on the node should be used. The profile must be preconfigured on the node to work. Must be a descending path, relative to the kubelet's configured seccomp profile location. Must be set if type is "Localhost". Must NOT be set for any other type. ### [](#couchbaseclusters-spec-security-podsecuritycontext-seccompprofile-type)couchbaseclusters.spec.security.podSecurityContext.seccompProfile.type #### [](#constraints-248)Constraints **Required** **Type**: `string` #### [](#description-248)Description type indicates which kind of seccomp profile will be applied. Valid options are: Localhost - a profile defined in a file on the node should be used. RuntimeDefault - the container runtime default profile should be used. Unconfined - no profile should be applied. ### [](#couchbaseclusters-spec-security-podsecuritycontext-supplementalgroups)couchbaseclusters.spec.security.podSecurityContext.supplementalGroups #### [](#constraints-249)Constraints **Type**: `[]integer` #### [](#description-249)Description A list of groups applied to the first process run in each container, in addition to the container's primary GID, the fsGroup (if specified), and group memberships defined in the container image for the uid of the container process. If unspecified, no additional groups are added to any container. Note that group memberships defined in the container image for the uid of the container process are still effective, even if they are not included in this list. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-podsecuritycontext-sysctls)couchbaseclusters.spec.security.podSecurityContext.sysctls #### [](#constraints-250)Constraints **Type**: `[]object` #### [](#description-250)Description Sysctls hold a list of namespaced sysctls used for the pod. Pods with unsupported sysctls (by the container runtime) might fail to launch. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-podsecuritycontext-sysctls-name)couchbaseclusters.spec.security.podSecurityContext.sysctls.name #### [](#constraints-251)Constraints **Required** **Type**: `string` #### [](#description-251)Description Name of a property to set. ### [](#couchbaseclusters-spec-security-podsecuritycontext-sysctls-value)couchbaseclusters.spec.security.podSecurityContext.sysctls.value #### [](#constraints-252)Constraints **Required** **Type**: `string` #### [](#description-252)Description Value of a property to set. ### [](#couchbaseclusters-spec-security-podsecuritycontext-windowsoptions)couchbaseclusters.spec.security.podSecurityContext.windowsOptions #### [](#constraints-253)Constraints **Type**: `object` #### [](#description-253)Description The Windows specific settings applied to all containers. If unspecified, the options within a container's SecurityContext will be used. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is linux. ### [](#couchbaseclusters-spec-security-podsecuritycontext-windowsoptions-gmsacredentialspec)couchbaseclusters.spec.security.podSecurityContext.windowsOptions.gmsaCredentialSpec #### [](#constraints-254)Constraints **Type**: `string` #### [](#description-254)Description GMSACredentialSpec is where the GMSA admission webhook () inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field. ### [](#couchbaseclusters-spec-security-podsecuritycontext-windowsoptions-gmsacredentialspecname)couchbaseclusters.spec.security.podSecurityContext.windowsOptions.gmsaCredentialSpecName #### [](#constraints-255)Constraints **Type**: `string` #### [](#description-255)Description GMSACredentialSpecName is the name of the GMSA credential spec to use. ### [](#couchbaseclusters-spec-security-podsecuritycontext-windowsoptions-hostprocess)couchbaseclusters.spec.security.podSecurityContext.windowsOptions.hostProcess #### [](#constraints-256)Constraints **Type**: `boolean` #### [](#description-256)Description HostProcess determines if a container should be run as a 'Host Process' container. All of a Pod's containers must have the same effective HostProcess value (it is not allowed to have a mix of HostProcess containers and non-HostProcess containers). In addition, if HostProcess is true then HostNetwork must also be set to true. ### [](#couchbaseclusters-spec-security-podsecuritycontext-windowsoptions-runasusername)couchbaseclusters.spec.security.podSecurityContext.windowsOptions.runAsUserName #### [](#constraints-257)Constraints **Type**: `string` #### [](#description-257)Description The UserName in Windows to run the entrypoint of the container process. Defaults to the user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. ### [](#couchbaseclusters-spec-security-rbac)couchbaseclusters.spec.security.rbac #### [](#constraints-258)Constraints **Type**: `object` #### [](#description-258)Description RBAC is the options provided for enabling and selecting RBAC User resources to manage. ### [](#couchbaseclusters-spec-security-rbac-managed)couchbaseclusters.spec.security.rbac.managed #### [](#constraints-259)Constraints **Type**: `boolean` #### [](#description-259)Description Managed defines whether RBAC is managed by us or the clients. ### [](#couchbaseclusters-spec-security-rbac-selector)couchbaseclusters.spec.security.rbac.selector #### [](#constraints-260)Constraints **Type**: `object` #### [](#description-260)Description Selector is a label selector used to list RBAC resources in the namespace that are managed by the Operator. ### [](#couchbaseclusters-spec-security-securitycontext)couchbaseclusters.spec.security.securityContext #### [](#constraints-261)Constraints **Type**: `object` #### [](#description-261)Description SecurityContext defines the security options the container should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. Use securityContext.allowPrivilegeEscalation field to grant more privileges than its parent process. More info: . ### [](#couchbaseclusters-spec-security-securitycontext-allowprivilegeescalation)couchbaseclusters.spec.security.securityContext.allowPrivilegeEscalation #### [](#constraints-262)Constraints **Type**: `boolean` #### [](#description-262)Description AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no\_new\_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP\_SYS\_ADMIN Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-securitycontext-capabilities)couchbaseclusters.spec.security.securityContext.capabilities #### [](#constraints-263)Constraints **Type**: `object` #### [](#description-263)Description The capabilities to add/drop when running containers. Defaults to the default set of capabilities granted by the container runtime. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-securitycontext-capabilities-add)couchbaseclusters.spec.security.securityContext.capabilities.add #### [](#constraints-264)Constraints **Type**: `[]string` #### [](#description-264)Description Added capabilities. ### [](#couchbaseclusters-spec-security-securitycontext-capabilities-drop)couchbaseclusters.spec.security.securityContext.capabilities.drop #### [](#constraints-265)Constraints **Type**: `[]string` #### [](#description-265)Description Removed capabilities. ### [](#couchbaseclusters-spec-security-securitycontext-privileged)couchbaseclusters.spec.security.securityContext.privileged #### [](#constraints-266)Constraints **Type**: `boolean` #### [](#description-266)Description Run container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-securitycontext-procmount)couchbaseclusters.spec.security.securityContext.procMount #### [](#constraints-267)Constraints **Type**: `string` #### [](#description-267)Description procMount denotes the type of proc mount to use for the containers. The default is DefaultProcMount which uses the container runtime defaults for readonly paths and masked paths. This requires the ProcMountType feature flag to be enabled. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-securitycontext-readonlyrootfilesystem)couchbaseclusters.spec.security.securityContext.readOnlyRootFilesystem #### [](#constraints-268)Constraints **Type**: `boolean` #### [](#description-268)Description Whether this container has a read-only root filesystem. Default is false. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-securitycontext-runasgroup)couchbaseclusters.spec.security.securityContext.runAsGroup #### [](#constraints-269)Constraints **Type**: `integer` #### [](#description-269)Description The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-securitycontext-runasnonroot)couchbaseclusters.spec.security.securityContext.runAsNonRoot #### [](#constraints-270)Constraints **Type**: `boolean` #### [](#description-270)Description Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. ### [](#couchbaseclusters-spec-security-securitycontext-runasuser)couchbaseclusters.spec.security.securityContext.runAsUser #### [](#constraints-271)Constraints **Type**: `integer` #### [](#description-271)Description The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-securitycontext-selinuxoptions)couchbaseclusters.spec.security.securityContext.seLinuxOptions #### [](#constraints-272)Constraints **Type**: `object` #### [](#description-272)Description The SELinux context to be applied to the container. If unspecified, the container runtime will allocate a random SELinux context for each container. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-securitycontext-selinuxoptions-level)couchbaseclusters.spec.security.securityContext.seLinuxOptions.level #### [](#constraints-273)Constraints **Type**: `string` #### [](#description-273)Description Level is SELinux level label that applies to the container. ### [](#couchbaseclusters-spec-security-securitycontext-selinuxoptions-role)couchbaseclusters.spec.security.securityContext.seLinuxOptions.role #### [](#constraints-274)Constraints **Type**: `string` #### [](#description-274)Description Role is a SELinux role label that applies to the container. ### [](#couchbaseclusters-spec-security-securitycontext-selinuxoptions-type)couchbaseclusters.spec.security.securityContext.seLinuxOptions.type #### [](#constraints-275)Constraints **Type**: `string` #### [](#description-275)Description Type is a SELinux type label that applies to the container. ### [](#couchbaseclusters-spec-security-securitycontext-selinuxoptions-user)couchbaseclusters.spec.security.securityContext.seLinuxOptions.user #### [](#constraints-276)Constraints **Type**: `string` #### [](#description-276)Description User is a SELinux user label that applies to the container. ### [](#couchbaseclusters-spec-security-securitycontext-seccompprofile)couchbaseclusters.spec.security.securityContext.seccompProfile #### [](#constraints-277)Constraints **Type**: `object` #### [](#description-277)Description The seccomp options to use by this container. If seccomp options are provided at both the pod & container level, the container options override the pod options. Note that this field cannot be set when spec.os.name is windows. ### [](#couchbaseclusters-spec-security-securitycontext-seccompprofile-localhostprofile)couchbaseclusters.spec.security.securityContext.seccompProfile.localhostProfile #### [](#constraints-278)Constraints **Type**: `string` #### [](#description-278)Description localhostProfile indicates a profile defined in a file on the node should be used. The profile must be preconfigured on the node to work. Must be a descending path, relative to the kubelet's configured seccomp profile location. Must be set if type is "Localhost". Must NOT be set for any other type. ### [](#couchbaseclusters-spec-security-securitycontext-seccompprofile-type)couchbaseclusters.spec.security.securityContext.seccompProfile.type #### [](#constraints-279)Constraints **Required** **Type**: `string` #### [](#description-279)Description type indicates which kind of seccomp profile will be applied. Valid options are: Localhost - a profile defined in a file on the node should be used. RuntimeDefault - the container runtime default profile should be used. Unconfined - no profile should be applied. ### [](#couchbaseclusters-spec-security-securitycontext-windowsoptions)couchbaseclusters.spec.security.securityContext.windowsOptions #### [](#constraints-280)Constraints **Type**: `object` #### [](#description-280)Description The Windows specific settings applied to all containers. If unspecified, the options from the PodSecurityContext will be used. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Note that this field cannot be set when spec.os.name is linux. ### [](#couchbaseclusters-spec-security-securitycontext-windowsoptions-gmsacredentialspec)couchbaseclusters.spec.security.securityContext.windowsOptions.gmsaCredentialSpec #### [](#constraints-281)Constraints **Type**: `string` #### [](#description-281)Description GMSACredentialSpec is where the GMSA admission webhook () inlines the contents of the GMSA credential spec named by the GMSACredentialSpecName field. ### [](#couchbaseclusters-spec-security-securitycontext-windowsoptions-gmsacredentialspecname)couchbaseclusters.spec.security.securityContext.windowsOptions.gmsaCredentialSpecName #### [](#constraints-282)Constraints **Type**: `string` #### [](#description-282)Description GMSACredentialSpecName is the name of the GMSA credential spec to use. ### [](#couchbaseclusters-spec-security-securitycontext-windowsoptions-hostprocess)couchbaseclusters.spec.security.securityContext.windowsOptions.hostProcess #### [](#constraints-283)Constraints **Type**: `boolean` #### [](#description-283)Description HostProcess determines if a container should be run as a 'Host Process' container. All of a Pod's containers must have the same effective HostProcess value (it is not allowed to have a mix of HostProcess containers and non-HostProcess containers). In addition, if HostProcess is true then HostNetwork must also be set to true. ### [](#couchbaseclusters-spec-security-securitycontext-windowsoptions-runasusername)couchbaseclusters.spec.security.securityContext.windowsOptions.runAsUserName #### [](#constraints-284)Constraints **Type**: `string` #### [](#description-284)Description The UserName in Windows to run the entrypoint of the container process. Defaults to the user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. ### [](#couchbaseclusters-spec-security-uisessiontimeout)couchbaseclusters.spec.security.uiSessionTimeout #### [](#constraints-285)Constraints **Type**: `integer` **Default**: `0` **Minimum**: `0` **Maximum**: `16666` #### [](#description-285)Description UISessionTimeout sets how long, in minutes, before a user is declared inactive and signed out from the Couchbase Server UI. 0 represents no time out. ### [](#couchbaseclusters-spec-securitycontext)couchbaseclusters.spec.securityContext #### [](#constraints-286)Constraints **Type**: `object` #### [](#description-286)Description **DEPRECATED** \- by spec.security.securityContext SecurityContext allows the configuration of the security context for all Couchbase server pods. When using persistent volumes you may need to set the fsGroup field in order to write to the volume. For non-root clusters you must also set runAsUser to 1000, corresponding to the Couchbase user in official container images. More info: . ### [](#couchbaseclusters-spec-servergroups)couchbaseclusters.spec.serverGroups #### [](#constraints-287)Constraints **Type**: `[]string` #### [](#description-287)Description ServerGroups define the set of availability zones you want to distribute pods over, and construct Couchbase server groups for. By default, most cloud providers will label nodes with the key "topology.kubernetes.io/zone", the values associated with that key are used here to provide explicit scheduling by the Operator. You may manually label nodes using the "topology.kubernetes.io/zone" key, to provide failure-domain aware scheduling when none is provided for you. Global server groups are applied to all server classes, and may be overridden on a per-server class basis to give more control over scheduling and server groups. ### [](#couchbaseclusters-spec-servers)couchbaseclusters.spec.servers #### [](#constraints-288)Constraints **Required** **Type**: `[]object` **Minimum Items**: `1` #### [](#description-288)Description Servers defines server classes for the Operator to provision and manage. A server class defines what services are running and how many members make up that class. Specifying multiple server classes allows the Operator to provision clusters with Multi-Dimensional Scaling (MDS). At least one server class must be defined, and at least one server class must be running the data service. ### [](#couchbaseclusters-spec-servers-autoscaleenabled)couchbaseclusters.spec.servers.autoscaleEnabled #### [](#constraints-289)Constraints **Type**: `boolean` #### [](#description-289)Description AutoscaledEnabled defines whether the autoscaling feature is enabled for this class. When true, the Operator will create a CouchbaseAutoscaler resource for this server class. The CouchbaseAutoscaler implements the Kubernetes scale API and can be controlled by the Kubernetes horizontal pod autoscaler (HPA). ### [](#couchbaseclusters-spec-servers-env)couchbaseclusters.spec.servers.env #### [](#constraints-290)Constraints **Type**: `[]object` #### [](#description-290)Description Env allows the setting of environment variables in the Couchbase server container. ### [](#couchbaseclusters-spec-servers-envfrom)couchbaseclusters.spec.servers.envFrom #### [](#constraints-291)Constraints **Type**: `[]object` #### [](#description-291)Description EnvFrom allows the setting of environment variables in the Couchbase server container. ### [](#couchbaseclusters-spec-servers-image)couchbaseclusters.spec.servers.image #### [](#constraints-292)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(.*?(:\d+)?/)?.\*?/.*?(:.\*?\d+\.\d+\.\d+.\*|@sha256:[0-9a-f]{64})$` #### [](#description-292)Description Image is the container image name that will be used to launch Couchbase server instances in this server class. You cannot downgrade the Couchbase version. Across spec.image and all server classes there can only be two different Couchbase images. Updating this field to a value different than spec.image will cause an automatic upgrade of the server class. If it isn't specified then the cluster image will be used. ### [](#couchbaseclusters-spec-servers-name)couchbaseclusters.spec.servers.name #### [](#constraints-293)Constraints **Required** **Type**: `string` #### [](#description-293)Description Name is a textual name for the server configuration and must be unique. The name is used by the operator to uniquely identify a server class, and map pods back to an intended configuration. ### [](#couchbaseclusters-spec-servers-pod)couchbaseclusters.spec.servers.pod #### [](#constraints-294)Constraints **Type**: `object` #### [](#description-294)Description Pod defines a template used to create pod for each Couchbase server instance. Modifying pod metadata such as labels and annotations will update the pod in-place. Any other modification will result in a cluster upgrade in order to fulfill the request. The Operator reserves the right to modify or replace any field. More info: . ### [](#couchbaseclusters-spec-servers-resources)couchbaseclusters.spec.servers.resources #### [](#constraints-295)Constraints **Type**: `object` #### [](#description-295)Description Resources are the resource requirements for the Couchbase server container. This field overrides any automatic allocation as defined by `spec.autoResourceAllocation`. ### [](#couchbaseclusters-spec-servers-servergroups)couchbaseclusters.spec.servers.serverGroups #### [](#constraints-296)Constraints **Type**: `[]string` #### [](#description-296)Description ServerGroups define the set of availability zones you want to distribute pods over, and construct Couchbase server groups for. By default, most cloud providers will label nodes with the key "topology.kubernetes.io/zone", the values associated with that key are used here to provide explicit scheduling by the Operator. You may manually label nodes using the "topology.kubernetes.io/zone" key, to provide failure-domain aware scheduling when none is provided for you. Global server groups are applied to all server classes, and may be overridden on a per-server class basis to give more control over scheduling and server groups. ### [](#couchbaseclusters-spec-servers-services)couchbaseclusters.spec.servers.services #### [](#constraints-297)Constraints **Required** **Type**: `[]string` **Enumerations**: `admin, data, index, query, search, eventing, analytics` #### [](#description-297)Description Services is the set of Couchbase services to run on this server class. At least one class must contain the data service. The field may contain any of "data", "index", "query", "search", "eventing" or "analytics". Each service may only be specified once. ### [](#couchbaseclusters-spec-servers-size)couchbaseclusters.spec.servers.size #### [](#constraints-298)Constraints **Required** **Type**: `integer` **Minimum**: `1` #### [](#description-298)Description Size is the expected requested of the server class. This field must be greater than or equal to 1. ### [](#couchbaseclusters-spec-servers-volumemounts)couchbaseclusters.spec.servers.volumeMounts #### [](#constraints-299)Constraints **Type**: `object` #### [](#description-299)Description VolumeMounts define persistent volume claims to attach to pod. ### [](#couchbaseclusters-spec-servers-volumemounts-analytics)couchbaseclusters.spec.servers.volumeMounts.analytics #### [](#constraints-300)Constraints **Type**: `[]string` #### [](#description-300)Description AnalyticsClaims are persistent volumes that encompass analytics storage associated with the analytics service. Analytics claims can only be used on server classes running the analytics service, and must be used in conjunction with the default claim. This field allows the analytics service to use different storage media (e.g. SSD), and scale horizontally, to improve performance of this service. This field references a volume claim template name as defined in "spec.volumeClaimTemplates". ### [](#couchbaseclusters-spec-servers-volumemounts-data)couchbaseclusters.spec.servers.volumeMounts.data #### [](#constraints-301)Constraints **Type**: `string` #### [](#description-301)Description DataClaim is a persistent volume that encompasses key/value storage associated with the data service. The data claim can only be used on server classes running the data service, and must be used in conjunction with the default claim. This field allows the data service to use different storage media (e.g. SSD) to improve performance of this service. This field references a volume claim template name as defined in "spec.volumeClaimTemplates". ### [](#couchbaseclusters-spec-servers-volumemounts-default)couchbaseclusters.spec.servers.volumeMounts.default #### [](#constraints-302)Constraints **Type**: `string` #### [](#description-302)Description DefaultClaim is a persistent volume that encompasses all Couchbase persistent data, including document storage, indexes and logs. The default volume can be used with any server class. Use of the default claim allows the Operator to recover failed pods from the persistent volume far quicker than if the pod were using ephemeral storage. The default claim cannot be used at the same time as the logs claim within the same server class. This field references a volume claim template name as defined in "spec.volumeClaimTemplates". ### [](#couchbaseclusters-spec-servers-volumemounts-index)couchbaseclusters.spec.servers.volumeMounts.index #### [](#constraints-303)Constraints **Type**: `string` #### [](#description-303)Description IndexClaim s a persistent volume that encompasses index storage associated with the index and search services. The index claim can only be used on server classes running the index or search services, and must be used in conjunction with the default claim. This field allows the index and/or search service to use different storage media (e.g. SSD) to improve performance of this service. This field references a volume claim template name as defined in "spec.volumeClaimTemplates". Whilst this references index primarily, note that the full text search (FTS) service also uses this same mount. ### [](#couchbaseclusters-spec-servers-volumemounts-logs)couchbaseclusters.spec.servers.volumeMounts.logs #### [](#constraints-304)Constraints **Type**: `string` #### [](#description-304)Description LogsClaim is a persistent volume that encompasses only Couchbase server logs to aid with supporting the product. The logs claim can only be used on server classes running the following services: query, search & eventing. The logs claim cannot be used at the same time as the default claim within the same server class. This field references a volume claim template name as defined in "spec.volumeClaimTemplates". Whilst the logs claim can be used with the search service, the recommendation is to use the default claim for these. The reason for this is that a failure of these nodes will require indexes to be rebuilt and subsequent performance impact. ### [](#couchbaseclusters-spec-softwareupdatenotifications)couchbaseclusters.spec.softwareUpdateNotifications #### [](#constraints-305)Constraints **Type**: `boolean` #### [](#description-305)Description SoftwareUpdateNotifications enables software update notifications in the UI. When enabled, the UI will alert when a Couchbase server upgrade is available. ### [](#couchbaseclusters-spec-upgradeprocess)couchbaseclusters.spec.upgradeProcess #### [](#constraints-306)Constraints **Type**: `string` **Enumerations**: `SwapRebalance, DeltaRecovery, InPlaceUpgrade` #### [](#description-306)Description UpgradeProcess defines the process that will be used when performing a couchbase cluster upgrade. When SwapRebalance is requested (default), pods will be upgraded using either a RollingUpgrade or ImmediateUpgrade (determined by UpgradeStrategy). When InPlaceUpgrade is requested, the operator will perform an in-place upgrade on a best effort basis. InPlaceUpgrade cannot be used if the UpgradeStrategy is set to ImmediateUpgrade. ### [](#couchbaseclusters-spec-upgradestrategy)couchbaseclusters.spec.upgradeStrategy #### [](#constraints-307)Constraints **Type**: `string` **Enumerations**: `RollingUpgrade, ImmediateUpgrade` #### [](#description-307)Description UpgradeStrategy controls how aggressive the Operator is when performing a cluster upgrade. When a rolling upgrade is requested, pods are upgraded one at a time. This strategy is slower, however less disruptive. When an immediate upgrade strategy is requested, all pods are upgraded at the same time. This strategy is faster, but more disruptive. This field must be either "RollingUpgrade" or "ImmediateUpgrade", defaulting to "RollingUpgrade". ### [](#couchbaseclusters-spec-volumeclaimtemplates)couchbaseclusters.spec.volumeClaimTemplates #### [](#constraints-308)Constraints **Type**: `[]object` #### [](#description-308)Description VolumeClaimTemplates define the desired characteristics of a volume that can be requested/claimed by a pod, for example the storage class to use and the volume size. Volume claim templates are referred to by name by server class volume mount configuration. ### [](#couchbaseclusters-spec-xdcr)couchbaseclusters.spec.xdcr #### [](#constraints-309)Constraints **Type**: `object` #### [](#description-309)Description XDCR defines whether the Operator should manage XDCR, remote clusters and how to lookup replication resources. ### [](#couchbaseclusters-spec-xdcr-managed)couchbaseclusters.spec.xdcr.managed #### [](#constraints-310)Constraints **Type**: `boolean` #### [](#description-310)Description Managed defines whether XDCR is managed by the operator or not. ### [](#couchbaseclusters-spec-xdcr-remoteclusters)couchbaseclusters.spec.xdcr.remoteClusters #### [](#constraints-311)Constraints **Type**: `[]object` #### [](#description-311)Description RemoteClusters is a set of named remote clusters to establish replications to. ### [](#couchbaseclusters-spec-xdcr-remoteclusters-authenticationsecret)couchbaseclusters.spec.xdcr.remoteClusters.authenticationSecret #### [](#constraints-312)Constraints **Type**: `string` #### [](#description-312)Description AuthenticationSecret is a secret used to authenticate when establishing a remote connection. It is only required when not using mTLS. The secret must contain a username (secret key "username") and password (secret key "password"). ### [](#couchbaseclusters-spec-xdcr-remoteclusters-hostname)couchbaseclusters.spec.xdcr.remoteClusters.hostname #### [](#constraints-313)Constraints **Required** **Type**: `string` **Pattern (Regular Expression)**: `couchbase|http)(s)?(://?\b((25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)(\.|${4}\b)|([a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9\-]*[a-zA-Z0-9])\.)\*([A-Za-z0-9]|[A-Za-z0-9][A-Za-z0-9\-]*[A-Za-z0-9]|\[(\s\*([0-9A-Fa-f]{1,4}:){7}([0-9A-Fa-f]{1,4}|:|[0-9A-Fa-f]{1,4}:){6}(:[0-9A-Fa-f]{1,4}|((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d{3})|:))|[0-9A-Fa-f]{1,4}:){5}(((:[0-9A-Fa-f]{1,4}){1,2})|:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d{3})|:))|[0-9A-Fa-f]{1,4}:){4}(((:[0-9A-Fa-f]{1,4}){1,3})|((:[0-9A-Fa-f]{1,4})?:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d{3}))|:))|[0-9A-Fa-f]{1,4}:){3}(((:[0-9A-Fa-f]{1,4}){1,4})|((:[0-9A-Fa-f]{1,4}){0,2}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d{3}))|:))|[0-9A-Fa-f]{1,4}:){2}(((:[0-9A-Fa-f]{1,4}){1,5})|((:[0-9A-Fa-f]{1,4}){0,3}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d{3}))|:))|[0-9A-Fa-f]{1,4}:){1}(((:[0-9A-Fa-f]{1,4}){1,6})|((:[0-9A-Fa-f]{1,4}){0,4}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d{3}))|:))|(:(:[0-9A-Fa-f]{1,4}){1,7})|((:[0-9A-Fa-f]{1,4}){0,5}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d{3}))|:)))(%.+)?\s\*\]))(:[0-9]{0,5})?(\\{0,1}\?network=[&]+)?$` #### [](#description-313)Description Hostname is the connection string to use to connect the remote cluster. To use IPv6, place brackets (`[`, `]`) around the IPv6 value. ### [](#couchbaseclusters-spec-xdcr-remoteclusters-name)couchbaseclusters.spec.xdcr.remoteClusters.name #### [](#constraints-314)Constraints **Required** **Type**: `string` #### [](#description-314)Description Name of the remote cluster. Note that, -operator-managed is added as suffix by operator automatically to the name in order to diffrentiate from non operator managed remote clusters. ### [](#couchbaseclusters-spec-xdcr-remoteclusters-replications)couchbaseclusters.spec.xdcr.remoteClusters.replications #### [](#constraints-315)Constraints **Type**: `object` #### [](#description-315)Description Replications are replication streams from this cluster to the remote one. This field defines how to look up CouchbaseReplication resources. By default any CouchbaseReplication resources in the namespace will be considered. ### [](#couchbaseclusters-spec-xdcr-remoteclusters-replications-selector)couchbaseclusters.spec.xdcr.remoteClusters.replications.selector #### [](#constraints-316)Constraints **Type**: `object` #### [](#description-316)Description Selector allows CouchbaseReplication resources to be filtered based on labels. ### [](#couchbaseclusters-spec-xdcr-remoteclusters-tls)couchbaseclusters.spec.xdcr.remoteClusters.tls #### [](#constraints-317)Constraints **Type**: `object` #### [](#description-317)Description TLS if specified references a resource containing the necessary certificate data for an encrypted connection. ### [](#couchbaseclusters-spec-xdcr-remoteclusters-tls-secret)couchbaseclusters.spec.xdcr.remoteClusters.tls.secret #### [](#constraints-318)Constraints **Required** **Type**: `string` #### [](#description-318)Description Secret references a secret containing the CA certificate (data key "ca"), and optionally a client certificate (data key "certificate") and key (data key "key"). ### [](#couchbaseclusters-spec-xdcr-remoteclusters-uuid)couchbaseclusters.spec.xdcr.remoteClusters.uuid #### [](#constraints-319)Constraints **Required** **Type**: `string` **Pattern (Regular Expression)**: `^[0-9a-f]{32}$` #### [](#description-319)Description UUID of the remote cluster. The UUID of a CouchbaseCluster resource is advertised in the status.clusterId field of the resource. ## [](#couchbaseclusters-status)couchbaseclusters.status ### [](#constraints-320)Constraints **Type**: `object` ### [](#description-320)Description ClusterStatus defines any read-only status fields for the Couchbase server cluster. ### [](#couchbaseclusters-status-allocations)couchbaseclusters.status.allocations #### [](#constraints-321)Constraints **Type**: `[]object` #### [](#description-321)Description Allocations shows memory allocations within server classes. ### [](#couchbaseclusters-status-allocations-allocatedmemory)couchbaseclusters.status.allocations.allocatedMemory #### [](#constraints-322)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-322)Description AllocatedMemory defines the total memory allocated for constrained Couchbase services. More info: . ### [](#couchbaseclusters-status-allocations-allocatedmemorypercent)couchbaseclusters.status.allocations.allocatedMemoryPercent #### [](#constraints-323)Constraints **Type**: `integer` #### [](#description-323)Description AllocatedMemoryPercent is set when memory resources are requested and define how much of the requested memory is allocated to constrained Couchbase services. ### [](#couchbaseclusters-status-allocations-analyticsserviceallocation)couchbaseclusters.status.allocations.analyticsServiceAllocation #### [](#constraints-324)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-324)Description AnalyticsServiceAllocation is set when the analytics service is enabled for this class and defines how much memory this service consumes per pod. More info: . ### [](#couchbaseclusters-status-allocations-dataserviceallocation)couchbaseclusters.status.allocations.dataServiceAllocation #### [](#constraints-325)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-325)Description DataServiceAllocation is set when the data service is enabled for this class and defines how much memory this service consumes per pod. More info: . ### [](#couchbaseclusters-status-allocations-eventingserviceallocation)couchbaseclusters.status.allocations.eventingServiceAllocation #### [](#constraints-326)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-326)Description EventingServiceAllocation is set when the eventing service is enabled for this class and defines how much memory this service consumes per pod. More info: . ### [](#couchbaseclusters-status-allocations-indexserviceallocation)couchbaseclusters.status.allocations.indexServiceAllocation #### [](#constraints-327)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-327)Description IndexServiceAllocation is set when the index service is enabled for this class and defines how much memory this service consumes per pod. More info: . ### [](#couchbaseclusters-status-allocations-name)couchbaseclusters.status.allocations.name #### [](#constraints-328)Constraints **Required** **Type**: `string` #### [](#description-328)Description Name is the name of the server class defined in spec.servers. ### [](#couchbaseclusters-status-allocations-requestedmemory)couchbaseclusters.status.allocations.requestedMemory #### [](#constraints-329)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-329)Description RequestedMemory, if set, defines the Kubernetes resource request for the server class. More info: . ### [](#couchbaseclusters-status-allocations-searchserviceallocation)couchbaseclusters.status.allocations.searchServiceAllocation #### [](#constraints-330)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-330)Description SearchServiceAllocation is set when the search service is enabled for this class and defines how much memory this service consumes per pod. More info: . ### [](#couchbaseclusters-status-allocations-unusedmemory)couchbaseclusters.status.allocations.unusedMemory #### [](#constraints-331)Constraints **Type**: `string` **Pattern (Regular Expression)**: `^(\+|-)?[0-9]+(\.[0-9]*)?)|(\.[0-9]+[KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]\*)?)|(\.[0-9]+))?$` #### [](#description-331)Description UnusedMemory is set when memory resources are requested and is the difference between the requestedMemory and allocatedMemory. More info: . ### [](#couchbaseclusters-status-allocations-unusedmemorypercent)couchbaseclusters.status.allocations.unusedMemoryPercent #### [](#constraints-332)Constraints **Type**: `integer` #### [](#description-332)Description UnusedMemoryPercent is set when memory resources are requested and defines how much requested memory is not allocated. Couchbase server expects at least a 20% overhead. ### [](#couchbaseclusters-status-autoscalers)couchbaseclusters.status.autoscalers #### [](#constraints-333)Constraints **Type**: `[]string` #### [](#description-333)Description Autscalers describes all the autoscalers managed by the cluster. ### [](#couchbaseclusters-status-buckets)couchbaseclusters.status.buckets #### [](#constraints-334)Constraints **Type**: `[]object` #### [](#description-334)Description Buckets describes all the buckets managed by the cluster. ### [](#couchbaseclusters-status-buckets-compressionmode)couchbaseclusters.status.buckets.compressionMode #### [](#constraints-335)Constraints **Required** **Type**: `string` #### [](#description-335)Description CompressionMode defines how documents are compressed. ### [](#couchbaseclusters-status-buckets-conflictresolution)couchbaseclusters.status.buckets.conflictResolution #### [](#constraints-336)Constraints **Required** **Type**: `string` #### [](#description-336)Description ConflictResolution is relevant for `couchbase` and `ephemeral` bucket types and indicates how to resolve conflicts when using multi-master XDCR. ### [](#couchbaseclusters-status-buckets-enableflush)couchbaseclusters.status.buckets.enableFlush #### [](#constraints-337)Constraints **Required** **Type**: `boolean` #### [](#description-337)Description EnableFlush is whether a client can delete all documents in a bucket. ### [](#couchbaseclusters-status-buckets-enableindexreplica)couchbaseclusters.status.buckets.enableIndexReplica #### [](#constraints-338)Constraints **Required** **Type**: `boolean` #### [](#description-338)Description EnableIndexReplica is whether indexes against bucket documents are replicated. ### [](#couchbaseclusters-status-buckets-evictionpolicy)couchbaseclusters.status.buckets.evictionPolicy #### [](#constraints-339)Constraints **Required** **Type**: `string` #### [](#description-339)Description EvictionPolicy is relevant for `couchbase` and `ephemeral` bucket types and indicates how documents are evicted from memory when it is exhausted. ### [](#couchbaseclusters-status-buckets-iopriority)couchbaseclusters.status.buckets.ioPriority #### [](#constraints-340)Constraints **Required** **Type**: `string` #### [](#description-340)Description IoPriority is `low` or `high` depending on the number of threads spawned for data processing. ### [](#couchbaseclusters-status-buckets-memoryquota)couchbaseclusters.status.buckets.memoryQuota #### [](#constraints-341)Constraints **Required** **Type**: `integer` #### [](#description-341)Description BucketMemoryQuota is the bucket memory quota in megabytes. ### [](#couchbaseclusters-status-buckets-name)couchbaseclusters.status.buckets.name #### [](#constraints-342)Constraints **Required** **Type**: `string` #### [](#description-342)Description BucketName is the full name of the bucket. ### [](#couchbaseclusters-status-buckets-password)couchbaseclusters.status.buckets.password #### [](#constraints-343)Constraints **Required** **Type**: `string` #### [](#description-343)Description BucketPassword will never be populated. ### [](#couchbaseclusters-status-buckets-replicas)couchbaseclusters.status.buckets.replicas #### [](#constraints-344)Constraints **Required** **Type**: `integer` #### [](#description-344)Description BucketReplicas is the number of data replicas. ### [](#couchbaseclusters-status-buckets-storagebackend)couchbaseclusters.status.buckets.storageBackend #### [](#constraints-345)Constraints **Type**: `string` #### [](#description-345)Description BucketStorageBackend is the storage backend of the bucket. ### [](#couchbaseclusters-status-buckets-type)couchbaseclusters.status.buckets.type #### [](#constraints-346)Constraints **Required** **Type**: `string` #### [](#description-346)Description BucketType is the type of the bucket. ### [](#couchbaseclusters-status-clusterid)couchbaseclusters.status.clusterId #### [](#constraints-347)Constraints **Type**: `string` #### [](#description-347)Description ClusterID is the unique cluster UUID. This is generated every time a new cluster is created, so may vary over the lifetime of a cluster if it is recreated by disaster recovery mechanisms. ### [](#couchbaseclusters-status-conditions)couchbaseclusters.status.conditions #### [](#constraints-348)Constraints **Type**: `[]object` #### [](#description-348)Description Current service state of the Couchbase cluster. ### [](#couchbaseclusters-status-conditions-lasttransitiontime)couchbaseclusters.status.conditions.lastTransitionTime #### [](#constraints-349)Constraints **Type**: `string` #### [](#description-349)Description Last time the condition transitioned from one status to another. ### [](#couchbaseclusters-status-conditions-lastupdatetime)couchbaseclusters.status.conditions.lastUpdateTime #### [](#constraints-350)Constraints **Type**: `string` #### [](#description-350)Description Last time the condition status message updated. ### [](#couchbaseclusters-status-conditions-message)couchbaseclusters.status.conditions.message #### [](#constraints-351)Constraints **Type**: `string` #### [](#description-351)Description A human readable message indicating details about the transition. ### [](#couchbaseclusters-status-conditions-reason)couchbaseclusters.status.conditions.reason #### [](#constraints-352)Constraints **Type**: `string` #### [](#description-352)Description Unique, one-word, CamelCase reason for the condition's last transition. ### [](#couchbaseclusters-status-conditions-status)couchbaseclusters.status.conditions.status #### [](#constraints-353)Constraints **Required** **Type**: `string` #### [](#description-353)Description Status is the status of the condition. Can be one of True, False, Unknown. ### [](#couchbaseclusters-status-conditions-type)couchbaseclusters.status.conditions.type #### [](#constraints-354)Constraints **Required** **Type**: `string` **Enumerations**: `Available, Balanced, ManageConfig, Scaling, ScalingUp, ScalingDown, Upgrading, Hibernating, Error, AutoscaleReady, Synchronized` #### [](#description-354)Description Type is the type of condition. ### [](#couchbaseclusters-status-controlpaused)couchbaseclusters.status.controlPaused #### [](#constraints-355)Constraints **Type**: `boolean` #### [](#description-355)Description ControlPaused indicates if the Operator has acknowledged and paused the control of the cluster. ### [](#couchbaseclusters-status-currentversion)couchbaseclusters.status.currentVersion #### [](#constraints-356)Constraints **Type**: `string` #### [](#description-356)Description CurrentVersion is the current Couchbase version. This reflects the version of the whole cluster, therefore during upgrade, it is only updated when the upgrade has completed. ### [](#couchbaseclusters-status-groups)couchbaseclusters.status.groups #### [](#constraints-357)Constraints **Type**: `[]string` #### [](#description-357)Description Groups describes all the groups managed by the cluster. ### [](#couchbaseclusters-status-members)couchbaseclusters.status.members #### [](#constraints-358)Constraints **Type**: `object` #### [](#description-358)Description Members are the Couchbase members in the cluster. ### [](#couchbaseclusters-status-members-ready)couchbaseclusters.status.members.ready #### [](#constraints-359)Constraints **Type**: `[]string` #### [](#description-359)Description Ready are the Couchbase members that are clustered and ready to serve client requests. The member names are the same as the Couchbase pod names. ### [](#couchbaseclusters-status-members-unready)couchbaseclusters.status.members.unready #### [](#constraints-360)Constraints **Type**: `[]string` #### [](#description-360)Description Unready are the Couchbase members not clustered or unready to serve client requests. The member names are the same as the Couchbase pod names. ### [](#couchbaseclusters-status-size)couchbaseclusters.status.size #### [](#constraints-361)Constraints **Required** **Type**: `integer` #### [](#description-361)Description Size is the current size of the cluster in terms of pods. Individual pod status conditions are listed in the members status. ### [](#couchbaseclusters-status-users)couchbaseclusters.status.users #### [](#constraints-362)Constraints **Type**: `[]string` #### [](#description-362)Description Users describes all the users managed by the cluster.