K8S-3415 Updated helm chart to 2.7.0

charts/couchbase-operator/Chart.yaml

@@ -1,8 +1,8 @@
 apiVersion: v2
 name: couchbase-operator
 description: A Helm chart to deploy the Couchbase Autonomous Operator for easily deploying, managing, and maintaining Couchbase Clusters. Couchbase Server is a NoSQL document database with a distributed architecture for performance, scalability, and availability. It enables developers to build applications easier and faster by leveraging the power of SQL with the flexibility of JSON.
-version: 2.50.4
-appVersion: 2.5.0
+version: 2.70.0
+appVersion: 2.7.0
 type: application
 keywords:
 - couchbase

charts/couchbase-operator/values.yaml

@@ -20,7 +20,7 @@ couchbaseOperator:
   # -- Image specifies repository and tag of the Couchbase Operator container.
   image:
     repository: couchbase/operator
-    tag: 2.5.0
+    tag: 2.7.0
   # -- The policy for pulling images from the repository onto hosts.
   # The imagePullPolicy value defaults to IfNotPresent, which means
   # that images are only pulled if they’re not present on the Kubernetes node.
@@ -53,7 +53,7 @@ admissionController:
   # -- Image specifies repository and tag of the Couchbase Admission container.
   image:
     repository: couchbase/admission-controller
-    tag: 2.5.0
+    tag: 2.7.0
   # -- The policy for pulling images from the repository onto hosts.
   # The imagePullPolicy value defaults to IfNotPresent, which means
   # that images are only pulled if they’re not present on the Kubernetes node.
@@ -647,6 +647,13 @@ buckets:
     # https://kubernetes.io/docs/concepts/configuration/manage-resources-
     # containers/#resource-units-in-kubernetes
     memoryQuota: 100Mi
+    # -- Rank determines the bucket’s place in the order in which the rebalance
+    # process handles the buckets on the cluster. The higher a bucket’s assigned
+    # integer (in relation to the integers assigned other buckets), the sooner
+    # in the rebalance process the bucket is handled. This assignment of rank
+    # allows a cluster’s most mission-critical data to be rebalanced with top
+    # priority. This option is only supported for Couchbase Server 7.6.0+.
+    rank: 0
     # -- Replicas defines how many copies of documents Couchbase server
     # maintains.  This directly affects how fault tolerant a Couchbase cluster
     # is.  With a single replica, the cluster can tolerate one data pod going
@@ -675,9 +682,8 @@ buckets:
       resources: []
     # -- StorageBackend to be assigned to and used by the bucket. Only valid for
     # Couchbase Server 7.0.0 onward. Two different backend storage mechanisms
-    # can be used - "couchstore" or "magma", defaulting to "couchstore". This
-    # cannot be edited after bucket creation. Note: "magma" is only valid for
-    # Couchbase Server 7.1.0 onward.
+    # can be used - "couchstore" or "magma", defaulting to "couchstore". Note:
+    # "magma" is only valid for Couchbase Server 7.1.0 onward.
     storageBackend: couchstore
 
 # @default -- will be filled in as below
@@ -762,11 +768,13 @@ cluster:
     # 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.  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
+    # 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
@@ -835,6 +843,12 @@ cluster:
     # not result in data loss.  This field must be in the range 5-3600s,
     # defaulting to 120s. More info:  https://golang.org/pkg/time/#ParseDuration
     autoFailoverTimeout: 120s
+    # -- Data allows the data service to be configured.
+    data:
+      # -- 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.
+      minReplicasCount: 0
     # -- 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
@@ -865,6 +879,11 @@ cluster:
     indexStorageSetting: memory_optimized
     # -- Indexer allows the indexer to be configured.
     indexer:
+      # -- 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+.
+      enableShardAffinity: false
       # -- 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".
@@ -900,6 +919,93 @@ cluster:
     query:
       # -- BackfillEnabled allows the query service to backfill.
       backfillEnabled: true
+      # -- CBOEnabled specifies whether the cost-based optimizer is enabled.
+      # Defaults to true.
+      cboEnabled: true
+      # -- 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.
+      cleanupClientAttemptsEnabled: true
+      # -- CleanupLostAttemptsEnabled specifies the Query service takes part in
+      # the distributed cleanup process, and cleans up expired transactions
+      # created by any client. Defaults to true.
+      cleanupLostAttemptsEnabled: true
+      # -- CleanupWindow specifies how frequently the Query service checks its
+      # subset of active transaction records for cleanup. Defaults to 60s
+      cleanupWindow: 60s
+      # -- CompletedLimit sets the number of requests to be logged in the
+      # completed requests catalog. As new completed requests are added, old
+      # ones are removed.
+      completedLimit: 4000
+      # -- 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.
+      completedMaxPlanSize: '262144'
+      # -- CompletedTrackingAllRequests allows all requests to be tracked
+      # regardless of their time. This field requires `completedTrackingEnabled`
+      # to be true.
+      completedTrackingAllRequests: false
+      # -- CompletedTrackingEnabled allows completed requests to be tracked in
+      # the requests catalog.
+      completedTrackingEnabled: true
+      # -- 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.
+      completedTrackingThreshold: 7s
+      # -- LogLevel controls the verbosity of query logs. This field must be one
+      # of "debug", "trace", "info", "warn", "error", "severe", or "none",
+      # defaulting to "info".
+      logLevel: info
+      # -- 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.
+      maxParallelism: 1
+      # -- 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.
+      memoryQuota: '0'
+      # -- 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.
+      nodeQuotaValPercent: 67
+      # -- 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.
+      numActiveTransactionRecords: 1024
+      # -- 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
+      numCpus: 0
+      # -- PipelineBatch controls the number of items execution operators can
+      # batch for Fetch from the KV. Defaults to 16.
+      pipelineBatch: 16
+      # -- PipelineCap controls the maximum number of items each execution
+      # operator can buffer between various operators. Defaults to 512.
+      pipelineCap: 512
+      # -- 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.
+      preparedLimit: 16384
+      # -- ScapCan sets the maximum buffered channel size between the indexer
+      # client and the query service for index scans. Defaults to 512.
+      scanCap: 512
       # -- 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
@@ -911,6 +1017,20 @@ cluster:
       # requires `backfillEnabled` to be set to true in order to have any
       # effect. This field overrides `temporarySpace`.
       temporarySpaceUnlimited: false
+      # -- 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).
+      txTimeout: 0ms
+      # -- 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+.
+      useReplica: false
     # -- 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
@@ -961,7 +1081,8 @@ cluster:
       # https://docs.couchbase.com/server/current/manage/manage-security/manage-
       # auditing.html
       garbageCollection:
-        # Provide the sidecar configuration required (if so desired) to
+        # DEPRECATED - by spec.logging.audit.nativePruning for Couchbase Server
+        # 7.2.4+ Provide the sidecar configuration required (if so desired) to
         # automatically clean up audit logs.
         sidecar:
           # The minimum age of rotated log files to remove, defaults to one
@@ -982,6 +1103,10 @@ cluster:
       rotation:
         # The interval at which to rotate log files, defaults to 15 minutes.
         interval: 15m
+        # 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.
+        pruneAge: '0'
         # Size allows the specification of a rotation size for the log, defaults
         # to 20Mi. More info:
         # https://kubernetes.io/docs/concepts/configuration/manage-resources-
@@ -1024,7 +1149,8 @@ cluster:
         # validation is carried out as this can be any arbitrary repo and tag.
         # It will default to the latest supported version of Fluent Bit.
         image: couchbase/fluent-bit:1.2.1
-  # -- Monitoring defines any Operator managed integration into 3rd party
+  # -- DEPRECATED - By Couchbase Server metrics endpoint on version 7.0+
+  # Monitoring defines any Operator managed integration into 3rd party
   # monitoring infrastructure.
   monitoring: {}
   # -- Name of the cluster, defaults to name of chart release
@@ -1039,14 +1165,25 @@ cluster:
     # must also be enabled. The Operator reserves the right to modify or replace
     # any field.  More info:
     # https://kubernetes.io/docs/reference/generated/kubernetes-
-    # api/v1.21/#service-v1-core
+    # api/v1.28/#service-v1-core
     adminConsoleServiceTemplate:
       # -- ServiceSpec describes the attributes that a user creates on a
       # service.
       spec:
         type: NodePort
     adminConsoleServices:
     - data
+    # -- CloudNativeGateway is used to provision a gRPC gateway proxying a
+    # Couchbase cluster.
+    cloudNativeGateway:
+      # -- 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".
+      logLevel: info
+      # -- TerminationGracePeriodSeconds specifies the grace period for the
+      # container to terminate. Defaults to 75 seconds.
+      terminationGracePeriodSeconds: 75
     # -- DisableUIOverHTTP is used to explicitly enable and disable UI access
     # over the HTTP protocol.  If not specified, this field defaults to false.
     disableUIOverHTTP: false
@@ -1063,7 +1200,7 @@ cluster:
     # must also be enabled. The Operator reserves the right to modify or replace
     # any field.  More info:
     # https://kubernetes.io/docs/reference/generated/kubernetes-
-    # api/v1.21/#service-v1-core
+    # api/v1.28/#service-v1-core
     exposedFeatureServiceTemplate:
       # -- ServiceSpec describes the attributes that a user creates on a
       # service.
@@ -1116,14 +1253,10 @@ cluster:
       # cannot be set when spec.os.name is linux.
       windowsOptions:
         # HostProcess determines if a container should be run as a 'Host
-        # Process' container. This field is alpha-level and will only be honored
-        # by components that enable the WindowsHostProcessContainers feature
-        # flag. Setting this field without the feature flag will result in
-        # errors when validating the Pod. 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.
+        # 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.
         hostProcess: false
     # -- RBAC is the options provided for enabling and selecting RBAC User
     # resources to manage.
@@ -1176,7 +1309,7 @@ cluster:
       # cluster upgrade in order to fulfill the request. The Operator reserves
       # the right to modify or replace any field.  More info:
       # https://kubernetes.io/docs/reference/generated/kubernetes-
-      # api/v1.21/#pod-v1-core
+      # api/v1.28/#pod-v1-core
       pod:
         spec: {}
       services:

charts/couchbase-operator/values.yamltmpl

@@ -20,7 +20,7 @@ couchbaseOperator:
   # -- Image specifies repository and tag of the Couchbase Operator container.
   image:
     repository: couchbase/operator
-    tag: 2.5.0
+    tag: 2.7.0
   # -- The policy for pulling images from the repository onto hosts.
   # The imagePullPolicy value defaults to IfNotPresent, which means
   # that images are only pulled if they’re not present on the Kubernetes node.
@@ -53,7 +53,7 @@ admissionController:
   # -- Image specifies repository and tag of the Couchbase Admission container.
   image:
     repository: couchbase/admission-controller
-    tag: 2.5.0
+    tag: 2.7.0
   # -- The policy for pulling images from the repository onto hosts.
   # The imagePullPolicy value defaults to IfNotPresent, which means
   # that images are only pulled if they’re not present on the Kubernetes node.