Skip to content

K8S-4511: Update upgrade howto docs to include arbiter nodes in upgra… #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TimLFletcher merged 1 commit into from
Jan 15, 2026
Merged

K8S-4511: Update upgrade howto docs to include arbiter nodes in upgra… #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions modules/ROOT/pages/howto-couchbase-upgrade.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.