1 Answer
- Newest
- Most votes
- Most comments
0
Hi
Before Upgrade try to verify following:
- Check the Version release file to check features which may affect your applications, Github release file and
- Take a **backup **of your cluster configuration and any stateful data before proceeding.
Once you upgrade a cluster, you can't downgrade to a previous version. We recommend that, before you update to a new Kubernetes version, you review the information in Amazon EKS Kubernetes versions and also review in the update steps in this topic.
Upgrade :
Control Plane:
- you can use console or CLI or any IaC tool to upgrade the cluster, reference documentation
Worker Nodes: Managed Node Groups:
- Create new Node group with AMI
- AMI optimized with latest changes information is https://github.com/awslabs/amazon-eks-ami/releases
- Update node group: Change the configuration of your node group to use the new AMI you found.
- Update nodes gradually, not all at once, to avoid downtime.
Self-Managed Nodes: Upgrade packages: Use your operating system's tools (like apt-get or yum) to install the Kubernetes 1.29 packages. Drain and cordon: For each old node, temporarily block new pods from being scheduled and move existing pods away. Delete old nodes: Once empty
Fargate: No action needed: Fargate handles the upgrades for you automatically.
Relevant content
- asked 4 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 7 months ago