Skip to content
Merged
Changes from all commits
Commits
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
15 changes: 14 additions & 1 deletion modules/ROOT/pages/concept-upgrade.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down