ZeroDownTime/KubeZero
3
0
Fork 0
Code Issues 1 Pull Requests 21 Packages Projects Releases Wiki Activity
76575b8cd1
KubeZero/releases/v1.22
History
Stefan Reimer 76575b8cd1 fix: minor fixes
2022-04-12 15:23:33 +02:00
..
kubezero_121.sh ci: Reorg kubezero container build 2022-04-08 17:09:40 +02:00
kubezero.sh fix: minor fixes 2022-04-12 15:23:33 +02:00
migrate_argo.sh ci: Reorg kubezero container build 2022-04-08 17:09:40 +02:00
README.md ci: Reorg kubezero container build 2022-04-08 17:09:40 +02:00
upgrade_121.sh ci: Reorg kubezero container build 2022-04-08 17:09:40 +02:00

README.md

Ensure your Kube context points to the correct cluster !!!

  1. Trigger the cluster upgrade:
    ./upgrade_121.sh

  2. Upgrade CFN stacks for the control plane and all worker groups Change Kubernetes version in controller config from 1.20.X to 1.21.9

  3. Reboot controller(s) one by one Wait each time for controller to join and all pods running. Might take a while ...

  4. Patch current deployments, blocking ArgoCD otherwise
    ./kubezero_121.sh

  5. Migrate ArgoCD config for the cluster
    ./migrate_argo.sh <cluster/env/kubezero/application.yaml>
    Adjust as needed, eg. ensure eck-operator is enabled if needed.
    git add / commit / push
    Watch ArgoCD do its work.

  6. Replace worker nodes Eg. by doubling desired for each worker ASG,
    once all new workers joined, drain old workers one by one,
    finally reset desired for each worker ASG which will terminate the old workers.

Known issues

On old/current workers, until workers get replaced:

If pods seem stuck, eg. fluent-bit shows NotReady after control nodes have been upgraded
-> restart kube-proxy on the affected workers