Skip to content

Commit 8d2a61d

Browse files
fleet update orchestration enhancements
1 parent 63cf9e3 commit 8d2a61d

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/kubernetes-fleet/update-orchestration.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,12 @@ Platform admins managing Kubernetes fleets with large number of clusters often h
4848
> [!NOTE]
4949
> Update runs honor [planned maintenance windows](../aks/planned-maintenance.md) that you set at the AKS cluster level. For more information, see [planned maintenance across multiple member clusters](./concepts-update-orchestration.md#planned-maintenance) which explains how update runs handle member clusters that have been configured with planned maintenance windows.
5050
51+
52+
Update run supports two options for the sequence in which the clusters are upgraded:
53+
54+
- **One-by-one**: If you don't care about controlling the sequence in which the clusters are upgraded, `one-by-one` provides a simple approach to upgrade all member clusters of the fleet in sequence one-by-one
55+
- **Control sequence of clusters using update groups and stages** - If you want to control the sequence in which the clusters are upgraded, you can structure member clusters in update groups and update stages.
56+
5157
## Update all clusters one by one
5258

5359
### [Azure portal](#tab/azure-portal)

0 commit comments

Comments
 (0)