How to Clarify Pending AWS EKS Cluster Upgrade Status

Select Language:

The banner you see is telling you that your cluster is set for an automatic upgrade. This usually happens when your current Kubernetes version is nearing the end of its standard support period. Amazon EKS automatically schedules these upgrades to keep your system current and supported.

When it comes to your questions:

First, will there be any downtime during the upgrade? Generally, upgrading the control plane does not cause downtime. Amazon EKS updates the API server by bringing in new nodes with the latest Kubernetes version while keeping the existing ones running until the upgrade finishes.

However, there are some things to keep in mind:
– If your worker nodes are not set up to handle node evictions properly, some applications might experience temporary downtime during their upgrade.
– Using Pod disruption budgets can help limit interruptions.
– In larger clusters with lots of network activity, you might see some packet loss when certain add-ons are being updated.

Second, about the upgrade schedule: The automatic update is usually set for when your current Kubernetes version hits the end of its support period. Amazon EKS offers standard support for each minor version for about 14 months after it is released.

Third, if you want to delay the upgrade, you can change your cluster’s upgrade policy from “STANDARD” to “EXTENDED.” This puts your cluster into extended support, which adds up to 12 months beyond the regular support period—though it does come with additional costs per cluster hour. This gives you more control over when the upgrade happens.

Before you start any upgrade, whether automatic or manual, it’s a good idea to:
– Check the “Upgrade insights” section in the EKS console for any potential issues.
– Test your applications on the new Kubernetes version in a non-production environment.
– Make sure all your add-ons and worker nodes are compatible with the version you plan to upgrade to.

If you choose to do the upgrade yourself, remember to update the control plane first, then the add-ons, and finally the worker nodes. Following this sequence helps ensure a smooth process.

Sources for further information include guides on Amazon EKS upgrades, troubleshooting, and upgrade policies, which provide detailed instructions and best practices.