A Step-by-Step Guide to Upgrading AWS EKS Clusters from 1.29 to 1.30 Using the AWS Console

Keeping your Amazon Elastic Kubernetes Service (EKS) clusters up to date is essential for maintaining security and accessing the latest features. This guide walks you through upgrading your EKS cluster from version 1.29 to 1.30 using the AWS Management Console.

Prerequisites

Before starting the upgrade process, ensure you have:

• Access to the AWS Management Console with appropriate IAM permissions.

• A backup of your cluster’s critical data.

• Browser access to the Kubernetes dashboard (if configured).

Pre-Upgrade Checklist

1. Document Current Configuration

• Take screenshots of your current cluster configuration.

• Note down all add-ons and their versions.

• Document any custom configurations.

2. Review Compatibility

• Check your applications’ compatibility with Kubernetes 1.30.

• Review the AWS EKS documentation for version-specific changes.

• Verify add-on compatibility with the new version.

The Upgrade Process

The main steps for the upgrade are:

1. Upgrading the control plane.

2. Upgrading managed node groups.

3. Updating the autoscaler image.

4. Updating add-ons.

Step 1: Upgrading the Control Plane

1. Access the EKS Console

• Log in to the AWS Management Console.

• Navigate to Amazon EKS.

• Select Clusters from the left navigation panel.

• Click on your cluster name.

• In the Cluster configuration tab, locate the Kubernetes version section.

• Click Update now next to the version number.

• Select version 1.30 from the dropdown.

• Review the update warning and click Update.

3. Monitor the Upgrade

• Stay on the cluster details page.

• Watch the Status field for progress updates (typically 20–30 minutes).

• The status will change from Updating to Active when the upgrade is complete.

Step 2: Upgrading Managed Node Groups

1. Access Node Groups

• On your cluster’s details page, select the Compute tab.

• Navigate to the Node Groups section.

2. Upgrade the Existing Node Group (Rolling Update)

• Select the node group from the list.

• Click Update (available next to the node group version).

• Choose Kubernetes version 1.30 for the upgrade.

• Confirm the upgrade process.

Note: This method performs a rolling update, incrementally replacing nodes with the new version. This approach is considered the best practice for upgrading production environments, ensuring minimal disruption and seamless transitions.

3. Monitor the Upgrade Progress

• Check the node group’s Status in the console.

• Wait for the upgrade to complete. It will transition from Updating to Active when done.

4. Verify Node Status

• Use the kubectl get nodes command to check if the new nodes are running Kubernetes version 1.30.

• Ensure all nodes are in the Ready state.

5. (Optional) Use a New Node Group

If you prefer to create a new node group instead of upgrading in place:

• Add a New Node Group:

• Click Add node group in the Compute tab.

• Configure the new node group with version 1.30 and other settings.

• Create and wait for the new group to become Active.

• Migrate Workloads:

• Cordon and drain the old nodes using the CLI:

kubectl cordon <old-node-name>
kubectl drain <old-node-name> - ignore-daemonsets - delete-emptydir-data

• Remove the Old Node Group:

• Select the old node group and click Delete. Confirm and wait for the process to complete.

6. Post-Upgrade Verification

• Confirm workloads are running on the new node group or upgraded nodes.

• Verify with:

kubectl get nodes -o wide

Step 3: Updating Cluster Autoscaler Image:

Ensuring the Cluster Autoscaler is compatible with your upgraded Kubernetes version is crucial. Follow these steps:

Option 1: Using AWS Console

1. Locate Cluster Autoscaler Deployment

• Go to your EKS Cluster in the AWS Console.

• Click on the Workloads tab.

• Find the cluster-autoscaler deployment (usually in the kube-system namespace).

2. Update the Image

• Click on the deployment and choose Edit.

• Locate the container image field.

• Update the image to:

registry.k8s.io/autoscaling/cluster-autoscaler:v1.30.3

• Save the changes.

Option 2: Using kubectl

1. Open your terminal and run the following command:

kubectl -n kube-system set image deployment.apps/cluster-autoscaler \
cluster-autoscaler=registry.k8s.io/autoscaling/cluster-autoscaler:v1.30.3

Important Notes

• Version Match: The Cluster Autoscaler version must match the Kubernetes version (e.g., 1.30.x for Kubernetes 1.30).

• Update Order: Complete this step after upgrading the control plane but before upgrading node groups.

Post-Update Verification

1. Check if the Cluster Autoscaler is running correctly:

kubectl -n kube-system logs -f deployment.apps/cluster-autoscaler

2. Look for errors or any indications of issues.

Step 4: Upgrading Add-ons

To ensure compatibility with Kubernetes 1.30, update your add-ons using these steps:

Updating Add-ons via AWS Console

1. Access the Add-ons Section

• Navigate to your EKS Cluster in the AWS Console.

• Click on the Add-ons tab in the cluster details.

1. Update Each Add-on

• For each add-on:

• Click on the add-on name, select Edit.

• Choose the default version that compatible with Kubernetes 1.30.

• Click Update to apply changes.

Post-Upgrade Verification

1. Verify Cluster Version

• Go to the cluster overview page.

• Confirm the Kubernetes version is set to 1.30.

1. Verify Node Groups

• Ensure all nodes are running Kubernetes 1.30.

• Verify that node statuses are set to Ready in the Compute tab.

1. Verify Add-ons

• In the Add-ons tab, confirm:

• All add-ons are in an Active state.

• The versions are compatible with Kubernetes 1.30.

2. Verify Node Groups

• Ensure all nodes are running version 1.30 and have a Ready status.

3. Check Add-ons

• Confirm all add-ons are in an Active state and compatible with version 1.30.

Troubleshooting Common Issues

1. Update Fails to Start

• Check if your IAM permissions allow upgrades.

• Ensure no other active operations are blocking the upgrade.

• Review your service quotas.

2. Node Group Issues

• Verify capacity in the selected Availability Zones.

• Confirm AMI compatibility with the new version.

• Double-check subnet configurations.

3. Add-on Update Failures

• Use CloudWatch logs to identify errors.

• Ensure add-on roles have proper permissions.

• Manually update add-ons if necessary.

Best Practices for Smooth Upgrades

1. Timing the Upgrade

• Schedule upgrades during low-traffic periods.

• Allocate extra time for testing and validation.

• Prepare a rollback plan in case of issues.

2. Testing Strategy

• Create a test cluster mirroring your production environment.

• Perform upgrades on non-production workloads first.

• Validate application functionality after upgrading.

3. Documenting the Process

• Maintain detailed notes of the upgrade process.

• Record any issues encountered and their solutions.

• Update internal runbooks and procedures for future reference.

Conclusion

Upgrading your EKS cluster via the AWS Console simplifies Kubernetes infrastructure maintenance. By carefully planning and following these steps, you can confidently upgrade to version 1.30. This ensures access to the latest features, enhanced security, and minimized downtime.

After completing these steps, your EKS cluster will be supported until July 23, 2025. Happy upgrading, and see you next time! 🚀

Resources

• Understand the Kubernetes version lifecycle on EKS,
• **Cluster Autoscaler Chart, **https://github.com/kubernetes/autoscaler/releases
• Update existing cluster to new Kubernetes version.