mirror of
https://github.com/edgelesssys/constellation.git
synced 2024-10-01 01:36:09 -04:00
docs: document upgrade backup files (#2275)
* document backup files on upgrade Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com> * reword TF backup * Update docs/docs/workflows/upgrade.md Co-authored-by: Otto Bittner <cobittner@posteo.net> * Update docs/docs/workflows/upgrade.md Co-authored-by: Otto Bittner <cobittner@posteo.net> * Update docs/docs/workflows/upgrade.md Co-authored-by: Otto Bittner <cobittner@posteo.net> * Update upgrade.md Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com> --------- Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com> Co-authored-by: Otto Bittner <cobittner@posteo.net> Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com>
This commit is contained in:
parent
abd5cdf362
commit
49e5a17aec
@ -58,6 +58,10 @@ Image and Kubernetes upgrades take longer.
|
|||||||
For each node in your cluster, a new node has to be created and joined.
|
For each node in your cluster, a new node has to be created and joined.
|
||||||
The process usually takes up to ten minutes per node.
|
The process usually takes up to ten minutes per node.
|
||||||
|
|
||||||
|
When applying an upgrade, backup files of Constellation-managed Custom Resource Definitions, Custom Resources, and Terraform state are created.
|
||||||
|
You can use the Terraform state backup to restore previous resources in case an upgrade misconfigured or erroneously deleted a resource.
|
||||||
|
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.
|
||||||
|
|
||||||
## Check the status
|
## Check the status
|
||||||
|
|
||||||
Upgrades are asynchronous operations.
|
Upgrades are asynchronous operations.
|
||||||
|
Loading…
Reference in New Issue
Block a user