From 187feb9827531c278fa731d6f1cc9c8262ae0ff6 Mon Sep 17 00:00:00 2001 From: BenMotts Date: Mon, 12 Jan 2026 17:14:46 +0000 Subject: [PATCH] K8S-4511: Update upgrade howto docs to include arbiter nodes in upgrade order --- modules/ROOT/pages/howto-couchbase-upgrade.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/howto-couchbase-upgrade.adoc b/modules/ROOT/pages/howto-couchbase-upgrade.adoc index 085734f..30bdb35 100644 --- a/modules/ROOT/pages/howto-couchbase-upgrade.adoc +++ b/modules/ROOT/pages/howto-couchbase-upgrade.adoc @@ -218,12 +218,13 @@ spec: - index - data - query + - arbiter ---- <.> The version to which you want to upgrade. <.> The order type you want the Operator to use. <.> Define the sequence the Operator uses to upgrade services. The Operator orders pods that run multiple services by the first service listed in the sequence. -With this manifest, the Operator upgrades pods running the Index Service first, followed by the Data Service, and then the Query Service. +With this manifest, the Operator upgrades pods running the Index Service first, followed by the Data Service, arbiter nodes (those running node services), and then the Query Service. If the number of pods running a service is less than `spec.upgrade.rollingUpgrade.maxUpgradable`, the Operator does not upgrade pods from the next service in the list. -When the sequence does not include all services, the Operator upgrades pods running unlisted services by using the default order: data, query, index, search, analytics, and eventing. +When the sequence does not include all services, the Operator upgrades pods running unlisted services by using the default order: data, query, index, search, analytics, eventing and arbiter.