K8S-3415 Updated helm chart for 2.7.0

charts/couchbase-operator/README.md

@@ -151,7 +151,7 @@ for more information about customizing and managing your charts.
 | cluster.cluster.indexer.stableSnapshotInterval | string | `"5s"` | StableSnapshotInterval controls when disk indexes should be snapshotted. This defaults to 5s, and must be greater than or equal to 1ms. |
 | cluster.cluster.indexer.storageMode | string | `"memory_optimized"` | 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". |
 | cluster.cluster.indexer.threads | string | `nil` | 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. |
-| cluster.cluster.query | object | `{"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","nodeQuota":null,"nodeQuotaValPercent":67,"numActiveTransactionRecords":1024,"numCpus":0,"pipelineBatch":16,"pipelineCap":512,"preparedLimit":16384,"scanCap":512,"temporarySpace":"5Gi","temporarySpaceUnlimited":false,"timeout":null,"txTimeout":"0ms","useReplica":false}` | Query allows the query service to be configured. |
+| cluster.cluster.query | object | `{"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":null,"txTimeout":"0ms","useReplica":false}` | Query allows the query service to be configured. |
 | cluster.cluster.query.backfillEnabled | bool | `true` | BackfillEnabled allows the query service to backfill. |
 | cluster.cluster.query.cboEnabled | bool | `true` | CBOEnabled specifies whether the cost-based optimizer is enabled. Defaults to true. |
 | cluster.cluster.query.cleanupClientAttemptsEnabled | bool | `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. |
@@ -165,7 +165,6 @@ for more information about customizing and managing your charts.
 | cluster.cluster.query.logLevel | string | `"info"` | LogLevel controls the verbosity of query logs. This field must be one of "debug", "trace", "info", "warn", "error", "severe", or "none", defaulting to "info". |
 | cluster.cluster.query.maxParallelism | int | `1` | 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. |
 | cluster.cluster.query.memoryQuota | string | `"0"` | 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. |
-| cluster.cluster.query.nodeQuota | string | `nil` | NodeQuota 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. This field is only supported on CB versions 7.6.0+. |
 | cluster.cluster.query.nodeQuotaValPercent | int | `67` | 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. |
 | cluster.cluster.query.numActiveTransactionRecords | int | `1024` | 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. |
 | cluster.cluster.query.numCpus | int | `0` | 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 |
@@ -178,7 +177,7 @@ for more information about customizing and managing your charts.
 | cluster.cluster.query.timeout | string | `nil` | 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. |
 | cluster.cluster.query.txTimeout | string | `"0ms"` | 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). |
 | cluster.cluster.query.useReplica | bool | `false` | 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+. |
-| cluster.cluster.queryServiceMemoryQuota | string | `nil` | QueryServiceMemQuota is a dummy field.  By default, Couchbase server provides no memory resource constraints for the query service, so this has no effect on Couchbase server.  It is, however, 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: https://kubernetes.io/docs/concepts/configuration/manage-resources- containers/#resource-units-in-kubernetes |
+| cluster.cluster.queryServiceMemoryQuota | string | `nil` | 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: https://kubernetes.io/docs/concepts/configuration/manage-resources- containers/#resource-units-in-kubernetes 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. |
 | cluster.cluster.searchServiceMemoryQuota | string | `"256Mi"` | 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: https://kubernetes.io/docs/concepts/configuration/manage-resources- containers/#resource-units-in-kubernetes |
 | cluster.enableOnlineVolumeExpansion | bool | `false` | 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: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#resizing-an- in-use-persistentvolumeclaim   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:  https://kubernetes.io/docs/concepts/storage/persistent- volumes/#expanding-persistent-volumes-claims |
 | cluster.enablePreviewScaling | bool | `false` | DEPRECATED - This option only exists for backwards compatibility and no longer restricts autoscaling to ephemeral services. EnablePreviewScaling enables autoscaling for stateful services and buckets. |
@@ -256,7 +255,7 @@ for more information about customizing and managing your charts.
 | cluster.servers.default.services | list | `["data","index","query","search","analytics","eventing"]` | 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. |
 | cluster.servers.default.size | int | `3` | Size is the expected requested of the server class.  This field must be greater than or equal to 1. |
 | cluster.softwareUpdateNotifications | bool | `false` | SoftwareUpdateNotifications enables software update notifications in the UI. When enabled, the UI will alert when a Couchbase server upgrade is available. |
-| cluster.upgradeProcess | string | `nil` | 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 DeltaRecovery is requested, the operator will perform an in-place upgrade on a best effort basis. DeltaRecovery cannot be used if the UpgradeStrategy is set to ImmediateUpgrade. |
+| cluster.upgradeProcess | string | `nil` | 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. |
 | cluster.upgradeStrategy | string | `nil` | 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". |
 | cluster.volumeClaimTemplates | object | `{"metadata":{"annotations":null,"labels":null,"name":null},"spec":{"accessModes":null,"dataSourceRef":{"apiGroup":null,"kind":null,"name":null,"namespace":null},"resources":{"claims":{"name":null},"limits":null,"requests":null},"selector":{"matchExpressions":{"key":null,"operator":null,"values":null},"matchLabels":null},"storageClassName":null,"volumeMode":null,"volumeName":null}}` | 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. |
 | cluster.volumeClaimTemplates.metadata | object | `{"annotations":null,"labels":null,"name":null}` | Standard objects metadata.  This is a curated version for use with Couchbase resource templates. |