From 92726dad2afd2c43aa148d3144f5826b35174df3 Mon Sep 17 00:00:00 2001 From: Adrian Stobbe Date: Sat, 9 Sep 2023 15:26:18 +0200 Subject: [PATCH] doc: `--skip-flag` in the upgrade workflow (#2313) Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com> --- docs/docs/workflows/upgrade.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/docs/workflows/upgrade.md b/docs/docs/workflows/upgrade.md index 94fe4bb066..e0a33734a1 100644 --- a/docs/docs/workflows/upgrade.md +++ b/docs/docs/workflows/upgrade.md @@ -63,6 +63,13 @@ You can use the Terraform state backup to restore previous resources in case an You can use the Custom Resource (Definition) backup files to restore Custom Resources and Definitions manually (e.g., via `kubectl apply`) if the automatic migration of those resources fails. You can use the Helm charts to manually apply upgrades to the Kubernetes resources, should an upgrade fail. +:::note + +For advanced users: the upgrade consists of several phases that can be individually skipped through the `--skip-phases` flag. +The phases are `infrastracture` for the cloud resource management through Terraform, `helm` for the chart management of the microservices, `image` for OS image upgrades, and `k8s` for Kubernetes version upgrades. + +::: + ## Check the status Upgrades are asynchronous operations.