51 lines
1.7 KiB
Markdown
51 lines
1.7 KiB
Markdown
|
# KubeZero 1.27
|
||
|
|
|
||
|
|
## TODO
|
||
|
|
|
||
|
|
## What's new - Major themes
|
||
|
|
- all KubeZero and support AMIs based on latest Alpine 3.18.4
|
||
|
|
- updated and improved hardening of Istio Ingress Gateways
|
||
|
|
- moved ECK operator into new kubezero-operators module
|
||
|
|
- new, optional, OpenSearch operator
|
||
|
|
|
||
|
|
## Version upgrades
|
||
|
|
- cilium 1.14.4
|
||
|
|
- istio 1.19.4
|
||
|
|
|
||
|
|
### FeatureGates
|
||
|
|
- CustomCPUCFSQuotaPeriod
|
||
|
|
- MemoryQoS
|
||
|
|
|
||
|
|
# 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 <path to the argocd app kubezero yaml for THIS cluster>`
|
||
|
|
|
||
|
|
4. Review the kubezero-config and if all looks good commit the ArgoApp resouce for Kubezero via regular git
|
||
|
|
git add / commit / push `<cluster/env/kubezero/application.yaml>`
|
||
|
|
|
||
|
|
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 <return> on the still waiting upgrade script
|
||
|
|
|
||
|
|
8. Quickly head over to ArgoCD and sync the KubeZero main module as soon as possible to reduce potential back and forth in case ArgoCD has legacy state
|
||
|
|
|
||
|
|
|
||
|
|
## Known issues
|
||
|
|
So far so good.
|