From 1a583358b063a551444ff513833e856c38ca0689 Mon Sep 17 00:00:00 2001 From: Stefan Reimer Date: Mon, 4 Dec 2023 14:32:42 +0000 Subject: [PATCH] docs: split upgrade from version docs --- docs/upgrade.md | 29 +++++++++++++++++++++++++++++ docs/v1.27.md | 32 +------------------------------- 2 files changed, 30 insertions(+), 31 deletions(-) create mode 100644 docs/upgrade.md diff --git a/docs/upgrade.md b/docs/upgrade.md new file mode 100644 index 00000000..f33eab2f --- /dev/null +++ b/docs/upgrade.md @@ -0,0 +1,29 @@ +# KubeZero - Cluster upgrade + +`(No, really, you MUST read this before you upgrade)` + +Ensure your Kube context points to the correct cluster ! + +1. Review CFN config for controller and workers, no mandatory changes during this release though + +2. Upgrade CFN stacks for the control plane *ONLY* ! + Updating the workers CFN stacks would trigger rolling updates right away ! + +3. Trigger cluster upgrade: + `./admin/upgrade_cluster.sh ` + +4. Review the kubezero-config and if all looks good commit the ArgoApp resouce for Kubezero via regular git + git add / commit / push `` + +5. Reboot controller(s) one by one +Wait each time for controller to join and all pods running. +Might take a while ... + +6. Upgrade CFN stacks for the workers. + This in turn will trigger automated worker updates by evicting pods and launching new workers in a rolling fashion. + Grab a coffee and keep an eye on the cluster to be safe ... + Depending on your cluster size it might take a while to roll over all workers! + +7. Re-enable ArgoCD by hitting on the still waiting upgrade script + +8. Head to the ArgoCD UI and sync all KubeZero apps to verify all are synced successfully. diff --git a/docs/v1.27.md b/docs/v1.27.md index 49d3d02e..be607a0a 100644 --- a/docs/v1.27.md +++ b/docs/v1.27.md @@ -21,35 +21,5 @@ ### FeatureGates - CustomCPUCFSQuotaPeriod -# Upgrade -`(No, really, you MUST read this before you upgrade)` - -Ensure your Kube context points to the correct cluster ! - -1. Review CFN config for controller and workers, no mandatory changes during this release though - -2. Upgrade CFN stacks for the control plane *ONLY* ! - Updating the workers CFN stacks would trigger rolling updates right away ! - -3. Trigger cluster upgrade: - `./admin/upgrade_cluster.sh ` - -4. Review the kubezero-config and if all looks good commit the ArgoApp resouce for Kubezero via regular git - git add / commit / push `` - -5. Reboot controller(s) one by one -Wait each time for controller to join and all pods running. -Might take a while ... - -6. Upgrade CFN stacks for the workers. - This in turn will trigger automated worker updates by evicting pods and launching new workers in a rolling fashion. - Grab a coffee and keep an eye on the cluster to be safe ... - Depending on your cluster size it might take a while to roll over all workers! - -7. Re-enable ArgoCD by hitting on the still waiting upgrade script - -8. Head to the ArgoCD UI and sync all KubeZero apps to verify all are synced successfully. - - ## Known issues -So far so good. +None.