From 4644b6f90171d7155a6a6472147369dd621e58d2 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Thu, 11 Dec 2025 18:55:38 +0530 Subject: [PATCH 01/27] draft 1 of release notes for cao 2-9-0 --- modules/ROOT/pages/release-notes.adoc | 148 ++++++++++++++++++++++++-- preview/DOC-13826-preview.yml | 6 ++ 2 files changed, 144 insertions(+), 10 deletions(-) create mode 100644 preview/DOC-13826-preview.yml diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index bd4fb6b..ec6a5d8 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -1,19 +1,96 @@ [#release-290] -== Release 2.9.0 (November 2025) +== Release 2.9.0 (December 2025) -Couchbase Operator 2.9.0 was released in November 2025. +Couchbase Operator 2.9.0 was released in December 2025. This maintenance release contains fixes to issues. [#fixed-issues-v290] == Fixed Issues +*https://jira.issues.couchbase.com/browse/K8S-1537/[K8S-1537]*:: + +Cluster UUID is no longer required when creating Remote Cluster Connections. + +*https://jira.issues.couchbase.com/browse/K8S-2829/[K8S-2829]*:: + +The annotation `cao.couchbase.com/additionalArgs` can now be specified on CouchbaseBackup and CouchbaseRestore resources to pass additional cbbackupmgr arguments through to the container. + +*https://jira.issues.couchbase.com/browse/K8S-3016/[K8S-3016]*:: + +It is now possible to specify Couchbase Server’s Password Policy via the CouchbaseCluster resource. + +*https://jira.issues.couchbase.com/browse/K8S-3121/[K8S-3121]*:: + +You can now specify to preserve the CouchbaseBackupRestore resource upon completion of the Restore. + +*https://jira.issues.couchbase.com/browse/K8S-3153/[K8S-3153]*:: + +New TCP Tunables (tcpKeepAliveIdle, tcpKeepAliveInterval, tcpKeepAliveProbes, tcpUserTimeout) are now available by the CouchbaseCluster Resource when using Couchbase Server 8.0 + *https://jira.issues.couchbase.com/browse/K8S-3258/[K8S-3258]*:: Added a new `logging.configNameReleasePrefix` boolean to the helm chart. This defaults to false, but setting it to true will prefix the fluent-bit config with the release name. Setting this to true for existing clusters will trigger recreation of all pods so should only really be used for new clusters. +*https://jira.issues.couchbase.com/browse/K8S-3371/[K8S-3371]*:: + +It is now possible to specify environment variables for the CouchbaseBackup and CouchbaseBackupRestore pod to allow for cbbackumgr tuning. + +*https://jira.issues.couchbase.com/browse/K8S-3434/[K8S-3434]*:: + +`spec.monitoring` has been deprecated and will no longer attach an exporter side car to the Couchbase Server pod. + +*https://jira.issues.couchbase.com/browse/K8S-3535/[K8S-3535]*:: + +If `couchbasecluster.spec.buckets.managed` is false, restoring from backup will automatically create buckets. + +*https://jira.issues.couchbase.com/browse/K8S-3616/[K8S-3616]*:: + +New settings for buckets are now available on Couchbase Server 8.0 + +*https://jira.issues.couchbase.com/browse/K8S-3638/[K8S-3638]*:: + +You can now specify merge schedule on a CouchbaseBackup resource. + +*https://jira.issues.couchbase.com/browse/K8S-3646/[K8S-3646]*:: + +You can now set query service’s CompletedStreamSize via the CouchbaseCluster resource. + +*https://jira.issues.couchbase.com/browse/K8S-3650/[K8S-3650]*:: + + + +*https://jira.issues.couchbase.com/browse/K8S-3715/[K8S-3715]*:: + +Added RBAC roles for users to match new roles added in Couchbase Server 8.0 + +*https://jira.issues.couchbase.com/browse/K8S-3786/[K8S-3786]*:: + +You can now specify `default` and `disk_io_optimized` for data service reader threads. + +*https://jira.issues.couchbase.com/browse/K8S-3917/[K8S-3917]*:: + +You can now specify `overheadMemory` for autoResourceAllocation to specify a static amount of overhead. + +*https://jira.issues.couchbase.com/browse/K8S-3951/[K8S-3951]*:: + +In 2.8.1, we added `cao.couchbase.com/autoCompaction.magmaFragmentationPercentage`. +This ticket requires the value to be added to the CRD’s, and marked as deprecated (Or remove from the documentation) as an annotation. + +*https://jira.issues.couchbase.com/browse/K8S-4013/[K8S-4013]*:: + +It is now possible to disable DNS resolution verification when creating pods, prior to activating them within the cluster. + +*https://jira.issues.couchbase.com/browse/K8S-4016/[K8S-4016]*:: + +Fixed a bug that caused a panic when a member pod becomes unresponsive. + +*https://jira.issues.couchbase.com/browse/K8S-4028/[K8S-4028]*:: + +Added an upgrade stanza to the CouchbaseCluster resource to give users more control during upgrades. + *https://jira.issues.couchbase.com/browse/K8S-4091/[K8S-4091]*:: Updated the `spec.networking.addressFamily` field to accept `IPv4Only`, `IPv4Priority`, `IPv6Only` and `IPv6Priority`. @@ -39,30 +116,81 @@ If the cluster enters this condition, it will: * Optionally, reconciliation will be skipped until the manual intervention required state has been resolved, i.e. the issue that put the cluster into that condition has been fixed. +*https://jira.issues.couchbase.com/browse/K8S-4101/[K8S-4101]*:: + +Added support for Couchbase Server 8.0’s Encryption at Rest feature. + +*https://jira.issues.couchbase.com/browse/K8S-4108/[K8S-4108]*:: + +The CouchbaseUser resource now has an enabled flag to allow the disabling/enabling of users. + +*https://jira.issues.couchbase.com/browse/K8S-4109/[K8S-4109]*:: + +The CouchbaseUser resource now has a `couchbaseuser.spec.userPassword.requireInitialChange` field to allow administrators to require a password change upon first use. + +*https://jira.issues.couchbase.com/browse/K8S-4111/[K8S-4111]*:: + +CouchbaseBucket resources now have a `durabilityImpossibleFallback` that accepts values of `disabled` and `fallbackToActiveAck`. + +*https://jira.issues.couchbase.com/browse/K8S-4112/[K8S-4112]*:: + +Multiple settings were added to CouchbaseBucket resources to set XDCR Conflict Logging. + +*https://jira.issues.couchbase.com/browse/K8S-4114/[K8S-4114]*:: + +Added setting in CouchbaseCluster to allow auto-failover of Ephemeral Buckets with no replicas. + Supported for CouchbaseServer 8.0+ + +*https://jira.issues.couchbase.com/browse/K8S-4117/[K8S-4117]*:: + +Added `data.diskUsageLimit` to the CouchbaseCluster resource to enable Disk Usage Guardrails. + +*https://jira.issues.couchbase.com/browse/K8S-4118/[K8S-4118]*:: + +Added support for SDK Telemetry settings in Couchbase Server 8.0+ + +*https://jira.issues.couchbase.com/browse/K8S-4120/[K8S-4120]*:: + +The default storage engine and vBucketCount for CouchbaseBuckets has been changed to `magma` and `128` respectively. + *https://jira.issues.couchbase.com/browse/K8S-4144/[K8S-4144]*:: In prior versions of Couchbase Operator, the metrics port annotation (`prometheus.io/port`) was set to 8091, even if TLS was enabled. It will now correctly set to 18091. +*https://jira.issues.couchbase.com/browse/K8S-4158/[K8S-4158]*:: + +You can now specify to do an EvictionPolicy change while the bucket is online via swap rebalance. + *https://jira.issues.couchbase.com/browse/K8S-4161/[K8S-4161]*:: Operator 2.9.0 now allows you to set `spec.cluster.analytics.numReplicas`. This feature is only supported for couchbase server versions 7.6+. +*https://jira.issues.couchbase.com/browse/K8S-4209/[K8S-4209]*:: + +Full backups can now be resumed. + *https://jira.issues.couchbase.com/browse/K8S-4270/[K8S-4270]*:: Potentially where we use `kubectl apply` for CRDS, we add a note that this error is possible in 2.9+, and to add `--server-side` to the `kubectl apply` command. +*https://jira.issues.couchbase.com/browse/K8S-4273/[K8S-4273]*:: + +Fixed an issue where Operator would fail to remove pods from the cluster. + +*https://jira.issues.couchbase.com/browse/K8S-4279/[K8S-4279]*:: + +Fixed an issue where log message tags were inconsistent. + *https://jira.issues.couchbase.com/browse/K8S-4286/[K8S-4286]*:: -In the latest build, -the mirWatchdog feature is now set to off by default. -The sequence has been adjusted to move the skip function after the validationRunner, -and changes have been included in the CRD. -Additionally, -the system now skips the DAC during status changes. -These updates aim to streamline operations and improve efficiency. -// Generated by [chatgpt:gpt-4o] + + +*https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: + +[KnownIssue] The CouchbaseCluster CRD has grown to a size that does not allow client side apply to be used. + diff --git a/preview/DOC-13826-preview.yml b/preview/DOC-13826-preview.yml new file mode 100644 index 0000000..df721a3 --- /dev/null +++ b/preview/DOC-13826-preview.yml @@ -0,0 +1,6 @@ +sources: + docs-server: + branches: [release/8.0] + + docs-operator: + branches: [DOC-13826-release-notes-cao-2-9-0, release/2.9] \ No newline at end of file From 333593fdd3a5e0a5981ac86e2bd4a954f8d59086 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Thu, 11 Dec 2025 19:09:53 +0530 Subject: [PATCH 02/27] Updated preview file --- preview/DOC-13826-preview.yml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/preview/DOC-13826-preview.yml b/preview/DOC-13826-preview.yml index df721a3..2a18402 100644 --- a/preview/DOC-13826-preview.yml +++ b/preview/DOC-13826-preview.yml @@ -1,6 +1,7 @@ sources: - docs-server: - branches: [release/8.0] - docs-operator: - branches: [DOC-13826-release-notes-cao-2-9-0, release/2.9] \ No newline at end of file + branches: DOC-13826-release-notes-cao-2-9-0 + docs-server: + url: https://github.com/couchbase/docs-server.git + branches: master + startPaths: docs/ \ No newline at end of file From fb7788759b7b5b443f047c9958298d97fcf3828d Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Thu, 11 Dec 2025 20:15:12 +0530 Subject: [PATCH 03/27] Updated preview file-a --- preview/DOC-13826-preview.yml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/preview/DOC-13826-preview.yml b/preview/DOC-13826-preview.yml index 2a18402..0f46c4f 100644 --- a/preview/DOC-13826-preview.yml +++ b/preview/DOC-13826-preview.yml @@ -2,6 +2,4 @@ sources: docs-operator: branches: DOC-13826-release-notes-cao-2-9-0 docs-server: - url: https://github.com/couchbase/docs-server.git - branches: master - startPaths: docs/ \ No newline at end of file + branches: release/8.0 \ No newline at end of file From 136e13abe2a8f632ee2b0773607121d2b755ffd1 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Thu, 11 Dec 2025 20:26:03 +0530 Subject: [PATCH 04/27] testing preview --- preview/DOC-13826-preview.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/preview/DOC-13826-preview.yml b/preview/DOC-13826-preview.yml index 0f46c4f..922dec2 100644 --- a/preview/DOC-13826-preview.yml +++ b/preview/DOC-13826-preview.yml @@ -2,4 +2,6 @@ sources: docs-operator: branches: DOC-13826-release-notes-cao-2-9-0 docs-server: - branches: release/8.0 \ No newline at end of file + url: https://github.com/couchbase/docs-server.git + branches: release/8.0 + startPaths: docs/ \ No newline at end of file From c7a6896dda11616a7041ca1bbf559a41d09bc2b6 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Thu, 11 Dec 2025 22:08:19 +0530 Subject: [PATCH 05/27] RN regenerated --- modules/ROOT/pages/release-notes.adoc | 12 ++++-------- preview/DOC-13826-preview.yml | 6 +----- 2 files changed, 5 insertions(+), 13 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index ec6a5d8..d585761 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -60,7 +60,7 @@ You can now set query service’s CompletedStreamSize via the CouchbaseCluster r *https://jira.issues.couchbase.com/browse/K8S-3650/[K8S-3650]*:: - +When using Couchbase Server 8.0, You can no longer create Memcached buckets. *https://jira.issues.couchbase.com/browse/K8S-3715/[K8S-3715]*:: @@ -76,8 +76,7 @@ You can now specify `overheadMemory` for autoResourceAllocation to specify a sta *https://jira.issues.couchbase.com/browse/K8S-3951/[K8S-3951]*:: -In 2.8.1, we added `cao.couchbase.com/autoCompaction.magmaFragmentationPercentage`. -This ticket requires the value to be added to the CRD’s, and marked as deprecated (Or remove from the documentation) as an annotation. +`cao.couchbase.com/autoCompaction.magmaFragmentationPercentage` has been replaced with an entry in the Couchbase Cluster Resource Definition *https://jira.issues.couchbase.com/browse/K8S-4013/[K8S-4013]*:: @@ -160,7 +159,7 @@ In prior versions of Couchbase Operator, the metrics port annotation (`prometheu *https://jira.issues.couchbase.com/browse/K8S-4158/[K8S-4158]*:: -You can now specify to do an EvictionPolicy change while the bucket is online via swap rebalance. +You can now specify to perform an EvictionPolicy change while the bucket is online via swap rebalance. *https://jira.issues.couchbase.com/browse/K8S-4161/[K8S-4161]*:: @@ -171,10 +170,6 @@ This feature is only supported for couchbase server versions 7.6+. Full backups can now be resumed. -*https://jira.issues.couchbase.com/browse/K8S-4270/[K8S-4270]*:: - -Potentially where we use `kubectl apply` for CRDS, we add a note that this error is possible in 2.9+, and to add `--server-side` to the `kubectl apply` command. - *https://jira.issues.couchbase.com/browse/K8S-4273/[K8S-4273]*:: Fixed an issue where Operator would fail to remove pods from the cluster. @@ -190,6 +185,7 @@ Fixed an issue where log message tags were inconsistent. *https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: [KnownIssue] The CouchbaseCluster CRD has grown to a size that does not allow client side apply to be used. +Use `--server-side` when using `kubectl apply` diff --git a/preview/DOC-13826-preview.yml b/preview/DOC-13826-preview.yml index 922dec2..f4a1390 100644 --- a/preview/DOC-13826-preview.yml +++ b/preview/DOC-13826-preview.yml @@ -1,7 +1,3 @@ sources: docs-operator: - branches: DOC-13826-release-notes-cao-2-9-0 - docs-server: - url: https://github.com/couchbase/docs-server.git - branches: release/8.0 - startPaths: docs/ \ No newline at end of file + branches: DOC-13826-release-notes-cao-2-9-0 \ No newline at end of file From 84b65827533cab78447a2fbad64f933023ff3d1e Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Thu, 11 Dec 2025 22:38:56 +0530 Subject: [PATCH 06/27] testing preview 2 --- preview/DOC-13826-preview.yml | 3 --- preview/HEAD.yml | 2 +- 2 files changed, 1 insertion(+), 4 deletions(-) delete mode 100644 preview/DOC-13826-preview.yml diff --git a/preview/DOC-13826-preview.yml b/preview/DOC-13826-preview.yml deleted file mode 100644 index f4a1390..0000000 --- a/preview/DOC-13826-preview.yml +++ /dev/null @@ -1,3 +0,0 @@ -sources: - docs-operator: - branches: DOC-13826-release-notes-cao-2-9-0 \ No newline at end of file diff --git a/preview/HEAD.yml b/preview/HEAD.yml index 3736c35..6f6eeec 100644 --- a/preview/HEAD.yml +++ b/preview/HEAD.yml @@ -3,4 +3,4 @@ sources: branches: [release/8.0] docs-operator: - branches: [DOC-13656-Create-release-note-for-Couchbase-Operator-2.9.0, release/2.8] \ No newline at end of file + branches: [DOC-13826-release-notes-cao-2-9-0, release/2.8] \ No newline at end of file From 39e0ce01237f4b5cfa6e0043ed6eb20d4923f6cf Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Fri, 12 Dec 2025 06:52:25 +0530 Subject: [PATCH 07/27] Regenerated the updated release notes --- modules/ROOT/pages/release-notes.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index d585761..ca8b384 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -166,6 +166,10 @@ You can now specify to perform an EvictionPolicy change while the bucket is onli Operator 2.9.0 now allows you to set `spec.cluster.analytics.numReplicas`. This feature is only supported for couchbase server versions 7.6+. +*https://jira.issues.couchbase.com/browse/K8S-4203/[K8S-4203]*:: + +Fixed an issue where if many clusters are under management by Operator, the metrics scrape would be too large. + *https://jira.issues.couchbase.com/browse/K8S-4209/[K8S-4209]*:: Full backups can now be resumed. @@ -178,10 +182,6 @@ Fixed an issue where Operator would fail to remove pods from the cluster. Fixed an issue where log message tags were inconsistent. -*https://jira.issues.couchbase.com/browse/K8S-4286/[K8S-4286]*:: - - - *https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: [KnownIssue] The CouchbaseCluster CRD has grown to a size that does not allow client side apply to be used. From 30687747953a4b5851aa5937644ed6b84700f3ce Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Wed, 17 Dec 2025 13:39:57 +0530 Subject: [PATCH 08/27] Updated RN and generated whats new --- modules/ROOT/pages/release-notes.adoc | 22 ++++++++++++- modules/ROOT/pages/whats-new.adoc | 46 +++++++++++++++++---------- 2 files changed, 51 insertions(+), 17 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index ca8b384..8a83726 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -184,9 +184,29 @@ Fixed an issue where log message tags were inconsistent. *https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: -[KnownIssue] The CouchbaseCluster CRD has grown to a size that does not allow client side apply to be used. +The CouchbaseCluster CRD has grown to a size that does not allow client side apply to be used. Use `--server-side` when using `kubectl apply` +*https://jira.issues.couchbase.com/browse/K8S-4404/[K8S-4404]*:: +Fixed an issue where upgrades with SHA256 image digest definitions would be unsuccessful. + + +[#known-issues-290] +== Known Issues 2.9.0 (December 2025) + +For Couchbase Autonomous Operator 2.9.0 was released in December 2025, +these are the known issues that aren’t yet resolved. + + + + +[#dlist-known-issues-290-] +=== Operator + +*https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: + +The CouchbaseCluster CRD has grown to a size that does not allow client side apply to be used. +Use `--server-side` when using `kubectl apply` \ No newline at end of file diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index a36f045..0c48589 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -1,26 +1,40 @@ -= What's New? -include::partial$constants.adoc[] +[#whats-new-290] +== What's New in 2.9.0 (December 2025) -Autonomous Operator {operator-version-minor} introduces our new Cluster Migration functionality well as a number of other improvements and minor fixes. +Couchbase Operator 2.9.0 was released in December 2025. +New features and improvements are described below. -== Cluster Migration +== New Features -Cluster Migration allows you to transfer a currently-unmanaged Couchbase Server cluster over to being managed by the Operator, with zero downtime. -See xref:concept-migration.adoc[Couchbase Cluster Migration] for more details. -== Admission Controller Improvements -The Dynamic Admission Controller (DAC) will now warn if any cluster settings don't match our xref:best-practices.adoc#production-deployments[Best Practices for Production Deployments]. -The DAC will now prevent changes to the `CouchbaseCluster` spec while a hibernation is taking place. -If hibernation is enabled while a cluster is migrating, upgrading, scaling, or rebalancing, that process will conclude before the cluster enters hibernation. The DAC will warn when this is the case, and it will be visible in the operator logs. -To prevent any invalid resources failing to reconcile (i.e. if the DAC is not deployed in the current environment), the DAC Validation is now run at the beginning of the reconciliation loop. -Any invalid resources will be skipped for reconciliation, marked as `NotValid`, and logged. -== Miscellaneous Improvements +[#dlist-whats-new-290-] +=== Operator + +*https://jira.issues.couchbase.com/browse/K8S-3917/[K8S-3917]*:: + +You can now specify `overheadMemory` for autoResourceAllocation to specify a static amount of overhead. + +*https://jira.issues.couchbase.com/browse/K8S-4013/[K8S-4013]*:: + +It is now possible to disable DNS resolution verification when creating pods, prior to activating them within the cluster. + +*https://jira.issues.couchbase.com/browse/K8S-4028/[K8S-4028]*:: + +Added an upgrade stanza to the CouchbaseCluster resource to give users more control during upgrades. + +*https://jira.issues.couchbase.com/browse/K8S-4097/[K8S-4097]*:: + +The MirWatchdog is an out-of-band check that allows for additional alerting to be in place in the unlikely scenario that an Operator is unable to reconcile a cluster due to reasons outside of its controls/capabilities and which therefore require manual intervention by a user to resolve. Scenarios include but are not limited to, tls expiration, couchbase authentication errors and loss of quorum. +By default this is disabled, but can be enabled and configured using the `mirWatchdog` field in the couchbase cluster CRD. If the cluster enters this condition, it will: ++ +* Set the cluster_manual_intervention gauge metric to 1 +* Add (where possible) the `ManualInterventionRequired` condition to the cluster, with a message detailing the reason for entering the MIR state. +* Raise a `ManualInterventionRequired` Kubernetes event, with the event message set to the reason for entering manual intervention +* Optionally, reconciliation will be skipped until the manual intervention required state has been resolved, i.e. the issue that put the cluster into that condition has been fixed. + -* Pod Disruption Budgets can now be set per-Server Class by enabling xref:resource/couchbasecluster.adoc#couchbaseclusters-spec-perserviceclasspdb[`couchbaseclusters.spec.perServiceClassPDB`]. -* Sample Buckets can now be loaded via the xref:resource/couchbasebucket.adoc[`CouchbaseBucket`] resource, by using the xref:reference-annotations.adoc#cao-couchbase-comsamplebucket[`cao.couchbase.com/sampleBucket`] annotation. -* Query-related RBAC roles (`query_use_sequential_scans`, `query_use_sequences`, and `query_manage_sequences`) have now been added to xref:resource/couchbasegroup.adoc#couchbasegroups-spec-roles-name[`couchbasegroups.spec.roles.name`]. \ No newline at end of file From 7c4209c29680e88b20a2a25affeb103a27e4e7c4 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Wed, 17 Dec 2025 13:45:55 +0530 Subject: [PATCH 09/27] minor edit --- modules/ROOT/pages/release-notes.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index 8a83726..d809b24 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -195,7 +195,7 @@ Fixed an issue where upgrades with SHA256 image digest definitions would be unsu [#known-issues-290] -== Known Issues 2.9.0 (December 2025) +== Known Issues For Couchbase Autonomous Operator 2.9.0 was released in December 2025, these are the known issues that aren’t yet resolved. From 7d8d4a309e4849631b3c0b905756012c96b0c7af Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Wed, 17 Dec 2025 14:03:29 +0530 Subject: [PATCH 10/27] minor fix in RN main page --- modules/ROOT/pages/release-notes.adoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index d809b24..fb2b3aa 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -1,3 +1,11 @@ += Release Notes for Couchbase Kubernetes Operator 2.9.0 + +== New Features + +These release notes are focused on bug fixes and breaking changes. + +For information about new features and major improvements made in Couchbase Kubernetes Operator 2.9.0, see xref:whats-new.adoc[What's New]. + [#release-290] == Release 2.9.0 (December 2025) From 17f611f99545818a88b1f8f0261b874d4b17c3e6 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Wed, 17 Dec 2025 14:05:40 +0530 Subject: [PATCH 11/27] Minor edit in whatsnew --- modules/ROOT/pages/whats-new.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index 0c48589..808f306 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -4,6 +4,8 @@ Couchbase Operator 2.9.0 was released in December 2025. New features and improvements are described below. +For information about fixed and known issues, see the xref:release-notes.adoc[Release Notes]. + == New Features From 300aa2583435acfe5a97d1858bd4616cb97f89ed Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Wed, 17 Dec 2025 14:10:28 +0530 Subject: [PATCH 12/27] Another minor fix in whatsnew --- modules/ROOT/pages/whats-new.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index 808f306..c012d65 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -1,3 +1,8 @@ += What's New? + +The new features and major improvements made in Couchbase Kubernetes Operator 2.9.0 are described below. + + [#whats-new-290] == What's New in 2.9.0 (December 2025) From b3f553941c29e75a20bf27ed70f6dba80db3bc5a Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Wed, 17 Dec 2025 14:41:09 +0530 Subject: [PATCH 13/27] Formatting fixes --- modules/ROOT/pages/release-notes.adoc | 10 +++++----- modules/ROOT/pages/whats-new.adoc | 18 +++++------------- 2 files changed, 10 insertions(+), 18 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index fb2b3aa..b7aaa52 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -1,16 +1,16 @@ -= Release Notes for Couchbase Kubernetes Operator 2.9.0 += Release Notes for Couchbase Kubernetes Operator 2.9 == New Features These release notes are focused on bug fixes and breaking changes. -For information about new features and major improvements made in Couchbase Kubernetes Operator 2.9.0, see xref:whats-new.adoc[What's New]. +For information about new features and major improvements made in Couchbase Kubernetes Operator 2.9, see xref:whats-new.adoc[What's New]. [#release-290] -== Release 2.9.0 (December 2025) +== Release 2.9 (December 2025) -Couchbase Operator 2.9.0 was released in December 2025. -This maintenance release contains fixes to issues. +Couchbase Kubernetes Operator 2.9 was released in December 2025. +This release contains fixes to issues. [#fixed-issues-v290] == Fixed Issues diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index c012d65..fbf899f 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -1,22 +1,14 @@ -= What's New? += What's New in Couchbase Kubernetes Operator 2.9 -The new features and major improvements made in Couchbase Kubernetes Operator 2.9.0 are described below. - - -[#whats-new-290] -== What's New in 2.9.0 (December 2025) - -Couchbase Operator 2.9.0 was released in December 2025. +Couchbase Kubernetes Operator 2.9.0 was released in December 2025. New features and improvements are described below. For information about fixed and known issues, see the xref:release-notes.adoc[Release Notes]. -== New Features - - - - +[#whats-new-290] +== New Features and Enhancements in 2.9.0 +This release introduces the following new features. [#dlist-whats-new-290-] From 527bfca1761c37c51f6490a77b8b0347c7922d1d Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Fri, 19 Dec 2025 16:26:24 +0530 Subject: [PATCH 14/27] Added n edited whats new from PM --- modules/ROOT/pages/whats-new.adoc | 69 ++++++++++++++++++++++--------- 1 file changed, 50 insertions(+), 19 deletions(-) diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index fbf899f..4033e21 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -1,6 +1,6 @@ -= What's New in Couchbase Kubernetes Operator 2.9 += What's New in Couchbase Autonomous Operator 2.9 -Couchbase Kubernetes Operator 2.9.0 was released in December 2025. +Couchbase Autonomous Operator 2.9.0 was released in December 2025. New features and improvements are described below. For information about fixed and known issues, see the xref:release-notes.adoc[Release Notes]. @@ -8,32 +8,63 @@ For information about fixed and known issues, see the xref:release-notes.adoc[Re [#whats-new-290] == New Features and Enhancements in 2.9.0 -This release introduces the following new features. +Couchbase Autonomous Operator (CAO) 2.9.0 adds support for Couchbase Server 8.0 features and +introduces a circuit breaker called Manual Intervention Required (MIR) mode. +This release also improves the upgrade process by introducing a new upgrade object that enables more resilient automated upgrades. +=== Support for Couchbase Server 8.0 Features -[#dlist-whats-new-290-] -=== Operator +Couchbase Server 8.0 introduces several key features, listed in xref:server:introduction:whats-new.adoc[What's New in Version 8.0], which are now configurable through CAO 2.9.0. +These are the highlights: -*https://jira.issues.couchbase.com/browse/K8S-3917/[K8S-3917]*:: +* *Encryption at Rest:* Added support for a new `CouchbaseEncryptionKey` custom resource to manage encryption keys +and to specify which keys are used for each unit, such as buckets, configuration data, and logs. -You can now specify `overheadMemory` for autoResourceAllocation to specify a static amount of overhead. +* *Magma as the Default Storage Engine:* In Couchbase Server 8.0, magma with 128 vBuckets is the default storage engine for new buckets. +Therefore, for CouchbaseBuckets, now the default storage engine is `magma` and the vBucketCount is `128`. +Couchbase recommends setting the vBucket count to `1024` for high-throughput workloads. -*https://jira.issues.couchbase.com/browse/K8S-4013/[K8S-4013]*:: +* *XDCR Conflict Logging for Active-Active Setups:* Added multiple settings to the CouchbaseBucket resource to set up XDCR Conflict Logging. -It is now possible to disable DNS resolution verification when creating pods, prior to activating them within the cluster. +* Other features such as enabling and disabling user accounts, and new bucket settings such as for warmup. -*https://jira.issues.couchbase.com/browse/K8S-4028/[K8S-4028]*:: +=== Manual Intervention Required (MIR) Mode -Added an upgrade stanza to the CouchbaseCluster resource to give users more control during upgrades. +The MirWatchdog is an out-of-band check that provides additional alerting. +It's used when the Operator cannot reconcile a cluster due to reasons outside its control and requires manual user intervention. +Scenarios include TLS expiration, Couchbase authentication errors, and rebalance failures. -*https://jira.issues.couchbase.com/browse/K8S-4097/[K8S-4097]*:: +This feature is disabled by default but can be enabled and configured by using the `mirWatchdog` field in the CouchbaseCluster CRD. -The MirWatchdog is an out-of-band check that allows for additional alerting to be in place in the unlikely scenario that an Operator is unable to reconcile a cluster due to reasons outside of its controls/capabilities and which therefore require manual intervention by a user to resolve. Scenarios include but are not limited to, tls expiration, couchbase authentication errors and loss of quorum. -By default this is disabled, but can be enabled and configured using the `mirWatchdog` field in the couchbase cluster CRD. If the cluster enters this condition, it will: -+ -* Set the cluster_manual_intervention gauge metric to 1 -* Add (where possible) the `ManualInterventionRequired` condition to the cluster, with a message detailing the reason for entering the MIR state. -* Raise a `ManualInterventionRequired` Kubernetes event, with the event message set to the reason for entering manual intervention -* Optionally, reconciliation will be skipped until the manual intervention required state has been resolved, i.e. the issue that put the cluster into that condition has been fixed. +For more information, see xref:tutorial-mirwatchdog.adoc[Monitor for Manual Intervention Scenarios]. +=== Upgrade Process Improvements + +Autonomous upgrades now provide improved user input and control through a new `upgrade` object in the CouchbaseCluster specification, +which contains all configurations for upgrading a cluster. +The previous ServerClass image-based approach is now hard deprecated. + +This consolidation clarifies how to control and manage future upgrades. +All existing upgrade fields `upgradeProcess`, `upgradeStrategy`, and `rollingUpgrade` are deprecated, and moved under the `upgrade` object. + +The new `upgrade` object has the following new fields: + +* `UpgradeOrderType`: The unit of upgrade that can be a Node, ServerGroup, ServerClass, or Service. +* `UpgradeOrder`: The upgrade order of specified upgrade units. +* `stabilizationPeriod`: The wait time in seconds before upgrading the next unit. +* `previousVersionPodCount`: The number of pods to keep running on the previous version at the end of upgrade. + +For more information, see xref:concept-upgrade.adoc[Upgrade Couchbase Server] and xref:howto-couchbase-upgrade.adoc[Upgrade a Couchbase Deployment]. + +=== Other Improvements + +The following are additional important improvements: + +* Support for changing the bucket eviction policy online without requiring a bucket restart. +* The ability to disable DNS resolution verification when creating pods before activating them in the cluster. +* Support for specifying `overheadMemory` for `autoResourceAllocation` to define a static overhead amount. +* Operator-backup now supports Periodic Merge in addition to Full Only and Full Incremental. +This strategy is better suited for some larger clusters. +You can specify a merge schedule on the CouchbaseBackup resource. +* Support for specifying the `cao.couchbase.com/additionalArgs` annotation on CouchbaseBackup and CouchbaseRestore resources to pass additional `cbbackupmgr` arguments to the container. From df8a6a450f97c2e880a18ccfb23106f5d49cc0c5 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Fri, 19 Dec 2025 17:10:11 +0530 Subject: [PATCH 15/27] generated the edited n rewritten fixed issues --- modules/ROOT/pages/release-notes.adoc | 137 +++++++++++--------------- modules/ROOT/pages/whats-new.adoc | 4 +- 2 files changed, 61 insertions(+), 80 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index b7aaa52..0272aee 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -1,8 +1,8 @@ = Release Notes for Couchbase Kubernetes Operator 2.9 -== New Features +This page summarizes the fixes and changes in Couchbase Kubernetes Operator 2.9, and links to the associated issues and documentation. -These release notes are focused on bug fixes and breaking changes. +== New Features For information about new features and major improvements made in Couchbase Kubernetes Operator 2.9, see xref:whats-new.adoc[What's New]. @@ -13,115 +13,115 @@ Couchbase Kubernetes Operator 2.9 was released in December 2025. This release contains fixes to issues. [#fixed-issues-v290] -== Fixed Issues +== Fixed Issues in 2.9 +The issues fixed in this release are as follows. *https://jira.issues.couchbase.com/browse/K8S-1537/[K8S-1537]*:: -Cluster UUID is no longer required when creating Remote Cluster Connections. +The cluster UUID is no longer required when creating remote cluster connections. *https://jira.issues.couchbase.com/browse/K8S-2829/[K8S-2829]*:: -The annotation `cao.couchbase.com/additionalArgs` can now be specified on CouchbaseBackup and CouchbaseRestore resources to pass additional cbbackupmgr arguments through to the container. +You can now specify the `cao.couchbase.com/additionalArgs` annotation on CouchbaseBackup and CouchbaseRestore resources to pass additional `cbbackupmgr` arguments to the container. *https://jira.issues.couchbase.com/browse/K8S-3016/[K8S-3016]*:: -It is now possible to specify Couchbase Server’s Password Policy via the CouchbaseCluster resource. +You can now specify the Couchbase Server password policy using the CouchbaseCluster resource. *https://jira.issues.couchbase.com/browse/K8S-3121/[K8S-3121]*:: -You can now specify to preserve the CouchbaseBackupRestore resource upon completion of the Restore. +You can now specify to preserve the CouchbaseBackupRestore resource after the restore completes. *https://jira.issues.couchbase.com/browse/K8S-3153/[K8S-3153]*:: -New TCP Tunables (tcpKeepAliveIdle, tcpKeepAliveInterval, tcpKeepAliveProbes, tcpUserTimeout) are now available by the CouchbaseCluster Resource when using Couchbase Server 8.0 +New TCP tunables (`tcpKeepAliveIdle`, `tcpKeepAliveInterval`, `tcpKeepAliveProbes`, `tcpUserTimeout`) are now available through the CouchbaseCluster resource when using Couchbase Server 8.0. *https://jira.issues.couchbase.com/browse/K8S-3258/[K8S-3258]*:: -Added a new `logging.configNameReleasePrefix` boolean to the helm chart. -This defaults to false, but setting it to true will prefix the fluent-bit config with the release name. -Setting this to true for existing clusters will trigger recreation of all pods so should only really be used for new clusters. +Added the `logging.configNameReleasePrefix` boolean to the Helm chart. +The default value is `false`. +When set to `true`, the Operator prefixes the Fluent Bit configuration with the release name. ++ +Couchbase recommends enabling this setting only on new clusters because enabling it on existing clusters triggers recreation of all pods. *https://jira.issues.couchbase.com/browse/K8S-3371/[K8S-3371]*:: -It is now possible to specify environment variables for the CouchbaseBackup and CouchbaseBackupRestore pod to allow for cbbackumgr tuning. +You can now specify environment variables for the CouchbaseBackup and CouchbaseBackupRestore pods to allow `cbbackupmgr` tuning. *https://jira.issues.couchbase.com/browse/K8S-3434/[K8S-3434]*:: -`spec.monitoring` has been deprecated and will no longer attach an exporter side car to the Couchbase Server pod. +`spec.monitoring` is deprecated and no longer attaches an exporter sidecar to the Couchbase Server pod. *https://jira.issues.couchbase.com/browse/K8S-3535/[K8S-3535]*:: -If `couchbasecluster.spec.buckets.managed` is false, restoring from backup will automatically create buckets. +If `couchbasecluster.spec.buckets.managed` is set to `false`, restoring from backup automatically creates buckets. *https://jira.issues.couchbase.com/browse/K8S-3616/[K8S-3616]*:: -New settings for buckets are now available on Couchbase Server 8.0 +New REST API bucket settings for the Data Service are now available in Couchbase Server 8.0. *https://jira.issues.couchbase.com/browse/K8S-3638/[K8S-3638]*:: -You can now specify merge schedule on a CouchbaseBackup resource. +You can now specify a merge schedule on the CouchbaseBackup resource. *https://jira.issues.couchbase.com/browse/K8S-3646/[K8S-3646]*:: -You can now set query service’s CompletedStreamSize via the CouchbaseCluster resource. +You can now set the Query Service `CompletedStreamSize` using the CouchbaseCluster resource. *https://jira.issues.couchbase.com/browse/K8S-3650/[K8S-3650]*:: -When using Couchbase Server 8.0, You can no longer create Memcached buckets. +When using Couchbase Server 8.0, you can no longer create Memcached buckets. *https://jira.issues.couchbase.com/browse/K8S-3715/[K8S-3715]*:: -Added RBAC roles for users to match new roles added in Couchbase Server 8.0 +Added RBAC roles for users to match new roles added in Couchbase Server 8.0. *https://jira.issues.couchbase.com/browse/K8S-3786/[K8S-3786]*:: -You can now specify `default` and `disk_io_optimized` for data service reader threads. +You can now specify `default` and `disk_io_optimized` for the Data Service reader threads. *https://jira.issues.couchbase.com/browse/K8S-3917/[K8S-3917]*:: -You can now specify `overheadMemory` for autoResourceAllocation to specify a static amount of overhead. +You can now set `overheadMemory` for `autoResourceAllocation` to specify a static overhead amount. *https://jira.issues.couchbase.com/browse/K8S-3951/[K8S-3951]*:: -`cao.couchbase.com/autoCompaction.magmaFragmentationPercentage` has been replaced with an entry in the Couchbase Cluster Resource Definition +`cao.couchbase.com/autoCompaction.magmaFragmentationPercentage` has been replaced by a field in the CouchbaseCluster CRD. *https://jira.issues.couchbase.com/browse/K8S-4013/[K8S-4013]*:: -It is now possible to disable DNS resolution verification when creating pods, prior to activating them within the cluster. +You can now disable DNS resolution verification when creating pods before activating them in the cluster. *https://jira.issues.couchbase.com/browse/K8S-4016/[K8S-4016]*:: -Fixed a bug that caused a panic when a member pod becomes unresponsive. +Fixed a bug that caused a panic when a member pod became unresponsive. *https://jira.issues.couchbase.com/browse/K8S-4028/[K8S-4028]*:: -Added an upgrade stanza to the CouchbaseCluster resource to give users more control during upgrades. +Added an upgrade stanza to the CouchbaseCluster resource to give users more control over upgrades. *https://jira.issues.couchbase.com/browse/K8S-4091/[K8S-4091]*:: -Updated the `spec.networking.addressFamily` field to accept `IPv4Only`, `IPv4Priority`, `IPv6Only` and `IPv6Priority`. -The current `IPv4/IPv6` values will have the `Ipv4/6Only` functionality. -I.e. -customers that have set the fields will not see any change. - +Updated `spec.networking.addressFamily` to accept `IPv4Only`, `IPv4Priority`, `IPv6Only`, and `IPv6Priority`. +The existing `IPv4` and `IPv6` values retain the `IPv4Only` and `IPv6Only` behavior, so no change is required for existing configurations. ++ +These values are deprecated and will be removed in a future release. + -These should be considered deprecated and will be removed in a future release. - + -The priority/only choice determines whether `addressFamilyOnly` is true or false. +The priority or only option determines whether `addressFamilyOnly` is set to `true` or `false`. *https://jira.issues.couchbase.com/browse/K8S-4097/[K8S-4097]*:: -The MirWatchdog is an out-of-band check that allows for additional alerting to be in place in the unlikely scenario that an Operator is unable to reconcile a cluster due to reasons outside of its controls/capabilities and which therefore require manual intervention by a user to resolve. -Scenarios include but are not limited to, tls expiration, couchbase authentication errors and loss of quorum. -By default this is disabled, but can be enabled and configured using the `mirWatchdog` field in the couchbase cluster CRD. +The MirWatchdog is an out-of-band check that provides additional alerting. +It is used when the Operator cannot reconcile a cluster due to reasons outside its control and requires manual user intervention. +Scenarios include, but are not limited to, TLS expiration, Couchbase authentication errors, and loss of quorum. +This feature is disabled by default but can be enabled and configured by using the `mirWatchdog` field in the CouchbaseCluster CRD. If the cluster enters this condition, it will: + -* Set the cluster_manual_intervention gauge metric to 1 -* Add (where possible) the `ManualInterventionRequired` condition to the cluster, with a message detailing the reason for entering the MIR state. -* Raise a `ManualInterventionRequired` Kubernetes event, with the event message set to the reason for entering manual intervention -* Optionally, reconciliation will be skipped until the manual intervention required state has been resolved, i.e. -the issue that put the cluster into that condition has been fixed. +* Set the `cluster_manual_intervention` gauge metric to `1`. +* Add the `ManualInterventionRequired` condition to the cluster, where possible, with a message describing the reason for entering the MIR state. +* Raise a `ManualInterventionRequired` Kubernetes event, with the message describing the reason for entering manual intervention. +* Optionally, reconciliation is skipped until the manual intervention required state is resolved, that is, until the issue that caused the condition is fixed. *https://jira.issues.couchbase.com/browse/K8S-4101/[K8S-4101]*:: @@ -129,24 +129,23 @@ Added support for Couchbase Server 8.0’s Encryption at Rest feature. *https://jira.issues.couchbase.com/browse/K8S-4108/[K8S-4108]*:: -The CouchbaseUser resource now has an enabled flag to allow the disabling/enabling of users. +The CouchbaseUser resource now includes an `enabled` flag to allow administrators to enable or disable user accounts. *https://jira.issues.couchbase.com/browse/K8S-4109/[K8S-4109]*:: -The CouchbaseUser resource now has a `couchbaseuser.spec.userPassword.requireInitialChange` field to allow administrators to require a password change upon first use. +The CouchbaseUser resource now allows the administrators to enforce password change on a user’s first login using the `couchbaseuser.spec.userPassword.requireInitialChange` field. *https://jira.issues.couchbase.com/browse/K8S-4111/[K8S-4111]*:: -CouchbaseBucket resources now have a `durabilityImpossibleFallback` that accepts values of `disabled` and `fallbackToActiveAck`. +CouchbaseBucket resources now support `durabilityImpossibleFallback` with values `disabled` and `fallbackToActiveAck`. *https://jira.issues.couchbase.com/browse/K8S-4112/[K8S-4112]*:: -Multiple settings were added to CouchbaseBucket resources to set XDCR Conflict Logging. +Added multiple settings to CouchbaseBucket resources to configure XDCR Conflict Logging. *https://jira.issues.couchbase.com/browse/K8S-4114/[K8S-4114]*:: -Added setting in CouchbaseCluster to allow auto-failover of Ephemeral Buckets with no replicas. - Supported for CouchbaseServer 8.0+ +Added a CouchbaseCluster resource setting that enables auto‑failover of Ephemeral Buckets with no replicas in Couchbase Server 8.0 and later versions. *https://jira.issues.couchbase.com/browse/K8S-4117/[K8S-4117]*:: @@ -154,29 +153,30 @@ Added `data.diskUsageLimit` to the CouchbaseCluster resource to enable Disk Usag *https://jira.issues.couchbase.com/browse/K8S-4118/[K8S-4118]*:: -Added support for SDK Telemetry settings in Couchbase Server 8.0+ +Added support for SDK Telemetry settings in Couchbase Server 8.0 and later versions. *https://jira.issues.couchbase.com/browse/K8S-4120/[K8S-4120]*:: -The default storage engine and vBucketCount for CouchbaseBuckets has been changed to `magma` and `128` respectively. +For CouchbaseBuckets, now the default storage engine is `magma` and the vBucketCount is `128`. *https://jira.issues.couchbase.com/browse/K8S-4144/[K8S-4144]*:: -In prior versions of Couchbase Operator, the metrics port annotation (`prometheus.io/port`) was set to 8091, even if TLS was enabled. - It will now correctly set to 18091. +In the earlier versions of Couchbase Operator, the metrics port annotation `prometheus.io/port` was set to `8091`, even when TLS was enabled. + +It now correctly sets to `18091`. *https://jira.issues.couchbase.com/browse/K8S-4158/[K8S-4158]*:: -You can now specify to perform an EvictionPolicy change while the bucket is online via swap rebalance. +EvictionPolicy changes can now be applied to an online bucket during a swap rebalance. *https://jira.issues.couchbase.com/browse/K8S-4161/[K8S-4161]*:: -Operator 2.9.0 now allows you to set `spec.cluster.analytics.numReplicas`. -This feature is only supported for couchbase server versions 7.6+. +Operator 2.9.0 allows you to set `spec.cluster.analytics.numReplicas`. +This feature is supported only on Couchbase Server 7.6 and later versions. *https://jira.issues.couchbase.com/browse/K8S-4203/[K8S-4203]*:: -Fixed an issue where if many clusters are under management by Operator, the metrics scrape would be too large. +Fixed an issue where metrics scrapes became too large when the Operator managed many clusters. *https://jira.issues.couchbase.com/browse/K8S-4209/[K8S-4209]*:: @@ -184,7 +184,7 @@ Full backups can now be resumed. *https://jira.issues.couchbase.com/browse/K8S-4273/[K8S-4273]*:: -Fixed an issue where Operator would fail to remove pods from the cluster. +Fixed an issue where the Operator failed to remove pods from the cluster. *https://jira.issues.couchbase.com/browse/K8S-4279/[K8S-4279]*:: @@ -192,29 +192,10 @@ Fixed an issue where log message tags were inconsistent. *https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: -The CouchbaseCluster CRD has grown to a size that does not allow client side apply to be used. -Use `--server-side` when using `kubectl apply` +The CouchbaseCluster CRD now exceeds the size limit for client-side apply. +Use the `--server-side` option with `kubectl apply` to apply the resource. *https://jira.issues.couchbase.com/browse/K8S-4404/[K8S-4404]*:: -Fixed an issue where upgrades with SHA256 image digest definitions would be unsuccessful. - - - - -[#known-issues-290] -== Known Issues - -For Couchbase Autonomous Operator 2.9.0 was released in December 2025, -these are the known issues that aren’t yet resolved. - - - - -[#dlist-known-issues-290-] -=== Operator - -*https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: +Fixed an issue that caused upgrades to fail when image definitions used SHA256 digests. -The CouchbaseCluster CRD has grown to a size that does not allow client side apply to be used. -Use `--server-side` when using `kubectl apply` \ No newline at end of file diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index 4033e21..b4ee4d0 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -1,4 +1,4 @@ -= What's New in Couchbase Autonomous Operator 2.9 += What's New? Couchbase Autonomous Operator 2.9.0 was released in December 2025. New features and improvements are described below. @@ -6,7 +6,7 @@ New features and improvements are described below. For information about fixed and known issues, see the xref:release-notes.adoc[Release Notes]. [#whats-new-290] -== New Features and Enhancements in 2.9.0 +== New Features and Enhancements in CAO 2.9.0 Couchbase Autonomous Operator (CAO) 2.9.0 adds support for Couchbase Server 8.0 features and introduces a circuit breaker called Manual Intervention Required (MIR) mode. From 99acfa6ebe2ecd2a347821e1193cd72ffa1ffcab Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Fri, 19 Dec 2025 18:34:11 +0530 Subject: [PATCH 16/27] Minor formatting fixes --- modules/ROOT/pages/release-notes.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index 0272aee..1c7bf26 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -121,11 +121,11 @@ If the cluster enters this condition, it will: * Set the `cluster_manual_intervention` gauge metric to `1`. * Add the `ManualInterventionRequired` condition to the cluster, where possible, with a message describing the reason for entering the MIR state. * Raise a `ManualInterventionRequired` Kubernetes event, with the message describing the reason for entering manual intervention. -* Optionally, reconciliation is skipped until the manual intervention required state is resolved, that is, until the issue that caused the condition is fixed. +* Optionally, skips reconciliation until the manual intervention required state is resolved, that is, until the issue that caused the condition is fixed. *https://jira.issues.couchbase.com/browse/K8S-4101/[K8S-4101]*:: -Added support for Couchbase Server 8.0’s Encryption at Rest feature. +Added support for the Encryption at Rest feature of Couchbase Server 8.0. *https://jira.issues.couchbase.com/browse/K8S-4108/[K8S-4108]*:: @@ -162,7 +162,6 @@ For CouchbaseBuckets, now the default storage engine is `magma` and the vBucketC *https://jira.issues.couchbase.com/browse/K8S-4144/[K8S-4144]*:: In the earlier versions of Couchbase Operator, the metrics port annotation `prometheus.io/port` was set to `8091`, even when TLS was enabled. - It now correctly sets to `18091`. *https://jira.issues.couchbase.com/browse/K8S-4158/[K8S-4158]*:: From e1203adb759c9e12348258fa77d062fc3e4c85e6 Mon Sep 17 00:00:00 2001 From: rao-shwe Date: Fri, 19 Dec 2025 19:47:15 +0530 Subject: [PATCH 17/27] replace the term operator with kubernetes --- modules/ROOT/pages/whats-new.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index b4ee4d0..825eead 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -1,20 +1,20 @@ = What's New? -Couchbase Autonomous Operator 2.9.0 was released in December 2025. +Couchbase Kubernetes Operator 2.9.0 was released in December 2025. New features and improvements are described below. For information about fixed and known issues, see the xref:release-notes.adoc[Release Notes]. [#whats-new-290] -== New Features and Enhancements in CAO 2.9.0 +== New Features and Enhancements in 2.9.0 -Couchbase Autonomous Operator (CAO) 2.9.0 adds support for Couchbase Server 8.0 features and +Couchbase Kubernetes Operator 2.9.0 adds support for Couchbase Server 8.0 features and introduces a circuit breaker called Manual Intervention Required (MIR) mode. This release also improves the upgrade process by introducing a new upgrade object that enables more resilient automated upgrades. === Support for Couchbase Server 8.0 Features -Couchbase Server 8.0 introduces several key features, listed in xref:server:introduction:whats-new.adoc[What's New in Version 8.0], which are now configurable through CAO 2.9.0. +Couchbase Server 8.0 introduces several key features, listed in xref:server:introduction:whats-new.adoc[What's New in Version 8.0], which are now configurable through Couchbase Kubernetes Operator 2.9.0. These are the highlights: * *Encryption at Rest:* Added support for a new `CouchbaseEncryptionKey` custom resource to manage encryption keys From 1571caa17075901f009b87055847ce1d92cf5c53 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Sat, 20 Dec 2025 07:51:05 +0530 Subject: [PATCH 18/27] Added Known Issues --- modules/ROOT/pages/release-notes.adoc | 49 ++++++++++++++++++++++----- modules/ROOT/pages/whats-new.adoc | 2 +- 2 files changed, 41 insertions(+), 10 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index 1c7bf26..bcf0fa8 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -1,6 +1,6 @@ = Release Notes for Couchbase Kubernetes Operator 2.9 -This page summarizes the fixes and changes in Couchbase Kubernetes Operator 2.9, and links to the associated issues and documentation. +This page summarizes the fixes and known issues in Couchbase Kubernetes Operator 2.9, and links to the associated issues. == New Features @@ -10,12 +10,12 @@ For information about new features and major improvements made in Couchbase Kube == Release 2.9 (December 2025) Couchbase Kubernetes Operator 2.9 was released in December 2025. -This release contains fixes to issues. +This release contains fixes to issues and known issues. [#fixed-issues-v290] == Fixed Issues in 2.9 -The issues fixed in this release are as follows. +For Couchbase Kubernetes Operator 2.9 released in December 2025, these are the fixed issues. *https://jira.issues.couchbase.com/browse/K8S-1537/[K8S-1537]*:: @@ -118,10 +118,10 @@ Scenarios include, but are not limited to, TLS expiration, Couchbase authenticat This feature is disabled by default but can be enabled and configured by using the `mirWatchdog` field in the CouchbaseCluster CRD. If the cluster enters this condition, it will: + -* Set the `cluster_manual_intervention` gauge metric to `1`. -* Add the `ManualInterventionRequired` condition to the cluster, where possible, with a message describing the reason for entering the MIR state. -* Raise a `ManualInterventionRequired` Kubernetes event, with the message describing the reason for entering manual intervention. -* Optionally, skips reconciliation until the manual intervention required state is resolved, that is, until the issue that caused the condition is fixed. +. Set the `cluster_manual_intervention` gauge metric to `1`. +. Add the `ManualInterventionRequired` condition to the cluster, where possible, with a message describing the reason for entering the MIR state. +. Raise a `ManualInterventionRequired` Kubernetes event, with the message describing the reason for entering manual intervention. +. Optionally, skips reconciliation until the manual intervention required state is resolved, that is, until the issue that caused the condition is fixed. *https://jira.issues.couchbase.com/browse/K8S-4101/[K8S-4101]*:: @@ -189,12 +189,43 @@ Fixed an issue where the Operator failed to remove pods from the cluster. Fixed an issue where log message tags were inconsistent. +*https://jira.issues.couchbase.com/browse/K8S-4404/[K8S-4404]*:: + +Fixed an issue that caused upgrades to fail when image definitions used SHA256 digests. + +[#known-issues-29] +== Known Issues 2.9 + +For Couchbase Kubernetes Operator 2.9 released in December 2025, these are the known issues that aren’t yet resolved. + +*https://jira.issues.couchbase.com/browse/K8S-4456/[K8S-4456]*:: + +Operator must be paused when using `cao create pod`. +Otherwise, the Operator identifies the pod as foreign and removes it. + +*https://jira.issues.couchbase.com/browse/K8S-4448/[K8S-4448]*:: + +Changing the server groups applied to a server class while the Operator is recovering a pod can block reconciliation. + +*https://jira.issues.couchbase.com/browse/K8S-4445/[K8S-4445]*:: + +The CouchbaseRestore resource status may fail to update from Couchbase Backup containers. +This does not prevent the restore from occurring. + +*https://jira.issues.couchbase.com/browse/K8S-4436/[K8S-4436]*:: + +Upgrading the Couchbase Operator while the cluster is not fully upgraded causes the Operator to complete the cluster upgrade immediately. + +*https://jira.issues.couchbase.com/browse/K8S-4433/[K8S-4433]*:: + +When running in mixed mode and before the upgrade to 8.0 completes, creating a Memcached bucket can cause the Operator to fail reconciliation. + *https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: The CouchbaseCluster CRD now exceeds the size limit for client-side apply. Use the `--server-side` option with `kubectl apply` to apply the resource. -*https://jira.issues.couchbase.com/browse/K8S-4404/[K8S-4404]*:: +*https://jira.issues.couchbase.com/browse/K8S-3839/[K8S-3839]*:: -Fixed an issue that caused upgrades to fail when image definitions used SHA256 digests. +Removing a server group from a cluster that uses InPlaceUpgrades can cause the Operator to fail to reconcile the cluster. diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index 825eead..03c961e 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -20,7 +20,7 @@ These are the highlights: * *Encryption at Rest:* Added support for a new `CouchbaseEncryptionKey` custom resource to manage encryption keys and to specify which keys are used for each unit, such as buckets, configuration data, and logs. -* *Magma as the Default Storage Engine:* In Couchbase Server 8.0, magma with 128 vBuckets is the default storage engine for new buckets. +* *Magma as the Default Storage Engine:* In Couchbase Server 8.0, Magma with 128 vBuckets is the default storage engine for new buckets. Therefore, for CouchbaseBuckets, now the default storage engine is `magma` and the vBucketCount is `128`. Couchbase recommends setting the vBucket count to `1024` for high-throughput workloads. From 1dc616f6cb20bb37ffac7cf026cdd5393fd63d4f Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Sat, 20 Dec 2025 08:03:50 +0530 Subject: [PATCH 19/27] minor grammar fix --- modules/ROOT/pages/release-notes.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index bcf0fa8..b44cde9 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -194,7 +194,7 @@ Fixed an issue where log message tags were inconsistent. Fixed an issue that caused upgrades to fail when image definitions used SHA256 digests. [#known-issues-29] -== Known Issues 2.9 +== Known Issues in 2.9 For Couchbase Kubernetes Operator 2.9 released in December 2025, these are the known issues that aren’t yet resolved. From bf618b41a66a37b15b9b2fa124c4a22939916a49 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Sat, 20 Dec 2025 08:27:20 +0530 Subject: [PATCH 20/27] Additional sections --- modules/ROOT/pages/release-notes.adoc | 19 +++++++++++++++++-- modules/ROOT/pages/whats-new.adoc | 1 + 2 files changed, 18 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index b44cde9..902d60f 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -1,4 +1,5 @@ = Release Notes for Couchbase Kubernetes Operator 2.9 +:page-toclevels: 2 This page summarizes the fixes and known issues in Couchbase Kubernetes Operator 2.9, and links to the associated issues. @@ -13,7 +14,7 @@ Couchbase Kubernetes Operator 2.9 was released in December 2025. This release contains fixes to issues and known issues. [#fixed-issues-v290] -== Fixed Issues in 2.9 +=== Fixed Issues in 2.9 For Couchbase Kubernetes Operator 2.9 released in December 2025, these are the fixed issues. @@ -194,7 +195,7 @@ Fixed an issue where log message tags were inconsistent. Fixed an issue that caused upgrades to fail when image definitions used SHA256 digests. [#known-issues-29] -== Known Issues in 2.9 +=== Known Issues in 2.9 For Couchbase Kubernetes Operator 2.9 released in December 2025, these are the known issues that aren’t yet resolved. @@ -229,3 +230,17 @@ Use the `--server-side` option with `kubectl apply` to apply the resource. Removing a server group from a cluster that uses InPlaceUpgrades can cause the Operator to fail to reconcile the cluster. + +== Feedback + +You can have a big impact on future versions of the Operator (and its documentation) by providing Couchbase with your direct feedback and observations. +Please feel free to post your questions and comments to the https://forums.couchbase.com/c/couchbase-server/Kubernetes[Couchbase Forums]. + +== Licenses for Third-Party Components + +The complete list of licenses for Couchbase products is available on the https://www.couchbase.com/legal/agreements[Legal Agreements] page. +Couchbase is thankful to all of the individuals that have created these third-party components. + +== More Information + +* xref:server:release-notes:relnotes.adoc[Couchbase Server Release Notes] \ No newline at end of file diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index 03c961e..cc2407e 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -1,4 +1,5 @@ = What's New? +:page-toclevels: 2 Couchbase Kubernetes Operator 2.9.0 was released in December 2025. New features and improvements are described below. From de8cd202b767ef655449a39872caecfb453ac728 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Sat, 20 Dec 2025 08:43:08 +0530 Subject: [PATCH 21/27] Added link to Server docs --- modules/ROOT/pages/release-notes.adoc | 7 ++++--- modules/ROOT/pages/whats-new.adoc | 4 ++++ 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index 902d60f..03889d8 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -162,7 +162,7 @@ For CouchbaseBuckets, now the default storage engine is `magma` and the vBucketC *https://jira.issues.couchbase.com/browse/K8S-4144/[K8S-4144]*:: -In the earlier versions of Couchbase Operator, the metrics port annotation `prometheus.io/port` was set to `8091`, even when TLS was enabled. +In the earlier versions of Couchbase Kubernetes Operator, the metrics port annotation `prometheus.io/port` was set to `8091`, even when TLS was enabled. It now correctly sets to `18091`. *https://jira.issues.couchbase.com/browse/K8S-4158/[K8S-4158]*:: @@ -215,7 +215,7 @@ This does not prevent the restore from occurring. *https://jira.issues.couchbase.com/browse/K8S-4436/[K8S-4436]*:: -Upgrading the Couchbase Operator while the cluster is not fully upgraded causes the Operator to complete the cluster upgrade immediately. +Upgrading the Couchbase Kubernetes Operator while the cluster is not fully upgraded causes the Operator to complete the cluster upgrade immediately. *https://jira.issues.couchbase.com/browse/K8S-4433/[K8S-4433]*:: @@ -243,4 +243,5 @@ Couchbase is thankful to all of the individuals that have created these third-pa == More Information -* xref:server:release-notes:relnotes.adoc[Couchbase Server Release Notes] \ No newline at end of file +* xref:server:release-notes:relnotes.adoc[Couchbase Server Release Notes Version 8.0] +* xref:server:introduction:whats-new.adoc[What's New in Couchbase Server Version 8.0] \ No newline at end of file diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index cc2407e..d3f5336 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -69,3 +69,7 @@ This strategy is better suited for some larger clusters. You can specify a merge schedule on the CouchbaseBackup resource. * Support for specifying the `cao.couchbase.com/additionalArgs` annotation on CouchbaseBackup and CouchbaseRestore resources to pass additional `cbbackupmgr` arguments to the container. +== More Information + +* xref:server:introduction:whats-new.adoc[What's New in Couchbase Server Version 8.0] +* xref:server:release-notes:relnotes.adoc[Couchbase Server Release Notes Version 8.0] \ No newline at end of file From 6ed593e18516ad7884e6a810a54795e900aff1d2 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Sat, 20 Dec 2025 08:51:25 +0530 Subject: [PATCH 22/27] changed 2-9-0 to 2-9 for consistency --- modules/ROOT/pages/whats-new.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/ROOT/pages/whats-new.adoc b/modules/ROOT/pages/whats-new.adoc index d3f5336..48a10f5 100644 --- a/modules/ROOT/pages/whats-new.adoc +++ b/modules/ROOT/pages/whats-new.adoc @@ -1,21 +1,21 @@ = What's New? :page-toclevels: 2 -Couchbase Kubernetes Operator 2.9.0 was released in December 2025. +Couchbase Kubernetes Operator 2.9 was released in December 2025. New features and improvements are described below. For information about fixed and known issues, see the xref:release-notes.adoc[Release Notes]. [#whats-new-290] -== New Features and Enhancements in 2.9.0 +== New Features and Enhancements in 2.9 -Couchbase Kubernetes Operator 2.9.0 adds support for Couchbase Server 8.0 features and +Couchbase Kubernetes Operator 2.9 adds support for Couchbase Server 8.0 features and introduces a circuit breaker called Manual Intervention Required (MIR) mode. This release also improves the upgrade process by introducing a new upgrade object that enables more resilient automated upgrades. === Support for Couchbase Server 8.0 Features -Couchbase Server 8.0 introduces several key features, listed in xref:server:introduction:whats-new.adoc[What's New in Version 8.0], which are now configurable through Couchbase Kubernetes Operator 2.9.0. +Couchbase Server 8.0 introduces several key features, listed in xref:server:introduction:whats-new.adoc[What's New in Version 8.0], which are now configurable through Couchbase Kubernetes Operator 2.9. These are the highlights: * *Encryption at Rest:* Added support for a new `CouchbaseEncryptionKey` custom resource to manage encryption keys From 1a81e2958f3b2b7a429b226f87c63c7b19d1b9bc Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Mon, 22 Dec 2025 19:07:07 +0530 Subject: [PATCH 23/27] Listed and rewrote 8 more known issues --- modules/ROOT/pages/release-notes.adoc | 63 +++++++++++++++++++++------ 1 file changed, 49 insertions(+), 14 deletions(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index 03889d8..d88149d 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -199,36 +199,71 @@ Fixed an issue that caused upgrades to fail when image definitions used SHA256 d For Couchbase Kubernetes Operator 2.9 released in December 2025, these are the known issues that aren’t yet resolved. -*https://jira.issues.couchbase.com/browse/K8S-4456/[K8S-4456]*:: +*https://jira.issues.couchbase.com/browse/K8S-3839/[K8S-3839]*:: -Operator must be paused when using `cao create pod`. -Otherwise, the Operator identifies the pod as foreign and removes it. +Removing a server group from a cluster that uses InPlaceUpgrades can cause the Operator to fail to reconcile the cluster. -*https://jira.issues.couchbase.com/browse/K8S-4448/[K8S-4448]*:: +*https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: -Changing the server groups applied to a server class while the Operator is recovering a pod can block reconciliation. +The CouchbaseCluster CRD now exceeds the size limit for client-side apply. +Use the `--server-side` option with `kubectl apply` to apply the resource. + +*https://jira.issues.couchbase.com/browse/K8S-4433/[K8S-4433]*:: + +When running in mixed mode and before the upgrade to 8.0 completes, creating a Memcached bucket can cause the Operator to fail reconciliation. + +*https://jira.issues.couchbase.com/browse/K8S-4436/[K8S-4436]*:: + +Upgrading the Couchbase Kubernetes Operator while the cluster is not fully upgraded causes the Operator to complete the cluster upgrade immediately. *https://jira.issues.couchbase.com/browse/K8S-4445/[K8S-4445]*:: The CouchbaseRestore resource status may fail to update from Couchbase Backup containers. This does not prevent the restore from occurring. -*https://jira.issues.couchbase.com/browse/K8S-4436/[K8S-4436]*:: +*https://jira.issues.couchbase.com/browse/K8S-4448/[K8S-4448]*:: -Upgrading the Couchbase Kubernetes Operator while the cluster is not fully upgraded causes the Operator to complete the cluster upgrade immediately. +Changing the server groups applied to a server class while the Operator is recovering a pod can block reconciliation. -*https://jira.issues.couchbase.com/browse/K8S-4433/[K8S-4433]*:: +*https://jira.issues.couchbase.com/browse/K8S-4456/[K8S-4456]*:: -When running in mixed mode and before the upgrade to 8.0 completes, creating a Memcached bucket can cause the Operator to fail reconciliation. +Operator must be paused when using `cao create pod`. +Otherwise, the Operator identifies the pod as foreign and removes it. -*https://jira.issues.couchbase.com/browse/K8S-4349/[K8S-4349]*:: +*https://jira.issues.couchbase.com/browse/K8S-4469/[K8S-4469]*:: -The CouchbaseCluster CRD now exceeds the size limit for client-side apply. -Use the `--server-side` option with `kubectl apply` to apply the resource. +Editing a Couchbase bucket storage backend while enabling or disabling `BucketMigrationRoutines` on a CouchbaseCluster can trigger a race condition that leads to an unreconcilable state. -*https://jira.issues.couchbase.com/browse/K8S-3839/[K8S-3839]*:: +*https://jira.issues.couchbase.com/browse/K8S-4471/[K8S-4471]*:: -Removing a server group from a cluster that uses InPlaceUpgrades can cause the Operator to fail to reconcile the cluster. +When `spec.networking.addressFamily` is set to `IPv6Priority` or `IPv6Only`, the Operator creates the cluster Service as IPv4 SingleStack, which causes pod launch failures. +Patching the Service to `PreferDualStack` (IPv4, IPv6) allows the cluster to be created. + +*https://jira.issues.couchbase.com/browse/K8S-4474/[K8S-4474]*:: + +Attempting to change bucket settings during a storage backend migration causes the Operator to fail to reconcile the cluster. + +*https://jira.issues.couchbase.com/browse/K8S-4477/[K8S-4477]*:: + +The admission controller allows you to set the `collectionHistoryDefault` value on Couchstore buckets. +This setting has no effect on Couchstore buckets. + +*https://jira.issues.couchbase.com/browse/K8S-4486/[K8S-4486]*:: + +You can start a Couchbase Server upgrade while a Bucket Storage Backend Migration is in progress. +This can result in an unreconcilable state. + +*https://jira.issues.couchbase.com/browse/K8S-4487/[K8S-4487]*:: + +Manual Intervention Watchdog does not clear the rebalancing condition when entering the Manual Intervention Required condition. + +*https://jira.issues.couchbase.com/browse/K8S-4488/[K8S-4488]*:: + +Reconciliation can begin before the Manual Intervention Watchdog is fully disabled. + +*https://jira.issues.couchbase.com/browse/K8S-4490/[K8S-4490]*:: + +During stabilization, the Operator reconciles some CouchbaseCluster settings. == Feedback From d7d177e523be6e7cfc041bee0555f8ec954b71a7 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Tue, 23 Dec 2025 07:32:45 +0530 Subject: [PATCH 24/27] Added 5 more Known Issues --- modules/ROOT/pages/release-notes.adoc | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index d88149d..40614e8 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -263,7 +263,28 @@ Reconciliation can begin before the Manual Intervention Watchdog is fully disabl *https://jira.issues.couchbase.com/browse/K8S-4490/[K8S-4490]*:: -During stabilization, the Operator reconciles some CouchbaseCluster settings. +During stabilization, the Operator reconciles some, but not all CouchbaseCluster settings. + +*https://jira.issues.couchbase.com/browse/K8S-4496/[K8S-4496]*:: + +It is possible to set replicas lower than the minimum required for a CouchbaseCluster when using an Ephemeral bucket. + +*https://jira.issues.couchbase.com/browse/K8S-4497/[K8S-4497]*:: + +The dynamic admission controller treats the default bucket storage backend as Couchstore, even on 8.0 clusters. + +*https://jira.issues.couchbase.com/browse/K8S-4498/[K8S-4498]*:: + +The order of password policy updates and user password changes can affect whether the Operator can make these changes successfully. + +*https://jira.issues.couchbase.com/browse/K8S-4499/[K8S-4499]*:: + +It's possible to rotate admin credentials to a password that does not meet the cluster password policy, which can prevent the Operator from reconciling the cluster. + +*https://jira.issues.couchbase.com/browse/K8S-4504/[K8S-4504]*:: + +Setting reader and writer threads to `balanced` during an upgrade from Couchbase Server 7.6 to 8.0 can cause memcached to crash. +Removing the reader and writer thread settings from the CRD resolves the issue. == Feedback From a8fe96a9272cabb0baaf267aadb52f204e177be7 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Tue, 23 Dec 2025 11:00:54 +0530 Subject: [PATCH 25/27] Updated preview file --- preview/HEAD.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/preview/HEAD.yml b/preview/HEAD.yml index 645a3c1..8d1b8b0 100644 --- a/preview/HEAD.yml +++ b/preview/HEAD.yml @@ -3,4 +3,4 @@ sources: branches: [release/8.0] docs-operator: - branches: [release/2.9] + branches: [DOC-13826-release-notes-cao-2-9-0] From 74bd4c126edbe53d96cef7d6ff8310e7d80c7147 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Tue, 23 Dec 2025 19:59:15 +0530 Subject: [PATCH 26/27] Added 11 more Known Issues --- modules/ROOT/pages/release-notes.adoc | 43 +++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index 40614e8..f7b8a84 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -248,6 +248,10 @@ Attempting to change bucket settings during a storage backend migration causes t The admission controller allows you to set the `collectionHistoryDefault` value on Couchstore buckets. This setting has no effect on Couchstore buckets. +*https://jira.issues.couchbase.com/browse/K8S-4482/[K8S-4482]*:: + +Attempting to change the `evictionPolicy` setting during a storage backend migration while `OnlineEvictionPolicyChange` is `true` can lead to an unreconcilable state. + *https://jira.issues.couchbase.com/browse/K8S-4486/[K8S-4486]*:: You can start a Couchbase Server upgrade while a Bucket Storage Backend Migration is in progress. @@ -286,6 +290,45 @@ It's possible to rotate admin credentials to a password that does not meet the c Setting reader and writer threads to `balanced` during an upgrade from Couchbase Server 7.6 to 8.0 can cause memcached to crash. Removing the reader and writer thread settings from the CRD resolves the issue. +*https://jira.issues.couchbase.com/browse/K8S-4507/[K8S-4507]*:: + +Enabling shard affinity in mixed mode, before the cluster fully supports the setting, can cause the Operator to fail reconciliation. + +*https://jira.issues.couchbase.com/browse/K8S-4508/[K8S-4508]*:: + +The Operator may not clear the unreconcilable condition after the resource is fixed. + +*https://jira.issues.couchbase.com/browse/K8S-4509/[K8S-4509]*:: + +Holding a cluster in mixed mode between 7.2.x and 7.6.x can prevent the Operator from reconciling some cluster settings. + +*https://jira.issues.couchbase.com/browse/K8S-4510/[K8S-4510]*:: + +Remaining in mixed mode on older Couchbase Server versions can cause the Operator to log errors due to incorrect version checks. + +*https://jira.issues.couchbase.com/browse/K8S-4511/[K8S-4511]*:: + +You cannot currently specify Arbiter nodes in the services order during an upgrade. + +*https://jira.issues.couchbase.com/browse/K8S-4512/[K8S-4512]*:: + +The Operator can update Index Storage settings twice accidentally. + +*https://jira.issues.couchbase.com/browse/K8S-4514/[K8S-4514]*:: + +The Operator can update the Fluent Bit configuration accidentally. + +*https://jira.issues.couchbase.com/browse/K8S-4515/[K8S-4515]*:: + +While processing a bucket migration, the Operator does not send the correct online change flag for modifications to Couchbase Server when changing the Eviction Policy. + +*https://jira.issues.couchbase.com/browse/K8S-4520/[K8S-4520]*:: + +The admission controller allows encryption at rest to be enabled in mixed mode. + +*https://jira.issues.couchbase.com/browse/K8S-4521/[K8S-4521]*:: + +The admission controller allows use of the Couchbase User `spec.user` field for users that reference clusters not running version 8.0.0. == Feedback From f8fceb9fdfa60043534536b4a2c720d421e0ee86 Mon Sep 17 00:00:00 2001 From: Shwetha Rao Date: Tue, 23 Dec 2025 21:23:29 +0530 Subject: [PATCH 27/27] Added known issue for K8S 4485 --- modules/ROOT/pages/release-notes.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/modules/ROOT/pages/release-notes.adoc b/modules/ROOT/pages/release-notes.adoc index f7b8a84..bff6aec 100644 --- a/modules/ROOT/pages/release-notes.adoc +++ b/modules/ROOT/pages/release-notes.adoc @@ -252,6 +252,10 @@ This setting has no effect on Couchstore buckets. Attempting to change the `evictionPolicy` setting during a storage backend migration while `OnlineEvictionPolicyChange` is `true` can lead to an unreconcilable state. +*https://jira.issues.couchbase.com/browse/K8S-4485/[K8S-4485]*:: + +Manually editing a bucket’s storage backend with BucketMigrationRoutines disabled can prevent the Operator from reconciling the cluster. + *https://jira.issues.couchbase.com/browse/K8S-4486/[K8S-4486]*:: You can start a Couchbase Server upgrade while a Bucket Storage Backend Migration is in progress.