ZeroDownTime/KubeZero
3
0
Fork 0
Code Issues 1 Pull Requests 21 Packages Projects Releases Wiki Activity
96dc628d21
KubeZero/docs/v1.27.md

1.8 KiB
Raw Blame History

KubeZero 1.27

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
  • IPv6 support for Ingress
  • moved ECK operator into new kubezero-operators module
  • new, optional, OpenSearch operator
  • all instances now enforce IMDSv2

Fixes

  • kubectl top nodes works now using node-exporter metrics rather than cadvisor

Version upgrades

  • cilium 1.14.4
  • istio 1.19.4
  • fluent-bit 2.2.0
  • ArgoCD 2.9
  • Prometheus / Grafana

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 <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 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.