From d58b977e2b736a6eda5a0781875318ad40bacc10 Mon Sep 17 00:00:00 2001 From: Ray Offiah Date: Mon, 16 Feb 2026 11:38:09 +0000 Subject: [PATCH] [DOC-13212]: Improve Docs related to InPlaceUpgrades for Couchbase Autonomous Operator Added extra notes concerning `InPlaceUpgrade`. Signed-off-by: Ray Offiah --- modules/ROOT/pages/concept-upgrade.adoc | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/concept-upgrade.adoc b/modules/ROOT/pages/concept-upgrade.adoc index 5f880e9b..88db5678 100644 --- a/modules/ROOT/pages/concept-upgrade.adoc +++ b/modules/ROOT/pages/concept-upgrade.adoc @@ -68,9 +68,22 @@ During this time, the Operator marks the cluster as Mixed Mode, which may restri It determines how the Operator interprets `upgradeOrder` and must be set to Nodes, ServerGroups, ServerClasses, or Services. The Operator follows the sequence specified in `upgradeOrder` and applies the default ordering to any items not listed. -NOTE: `InPlaceUpgrade` can interrupt service and increase the risk of data loss. +[NOTE] +.Important information about `InPlaceUpgrade`. +==== + +`InPlaceUpgrade` can interrupt service and increase the risk of data loss. Use this process only when the cluster has at least two nodes running the Data Service. +InplaceUpgrades can only be done performed one pod at a time. +This is due to restrictions by Couchbase Server’s delta recovery logic, which fails if any pod topology changes occur since the pod was gracefully failed. + +InPlaceUpgrades cannot be performed on single node clusters. +This is considered an “offline” upgrade, and will only work in 2.7.0+ +(See https://jira.issues.couchbase.com/browse/K8S-3542[K8S-3542]). + +==== + === How to Upgrade a Cluster To upgrade a cluster, modify the CouchbaseCluster manifest by setting the `spec.image` field to the Couchbase Server version you want.