~/ nmadiraju.com Amazon EKS · Cluster upgrades
arrow_back Back to nmadiraju
Visual Walkthrough · Cluster operations

How Cluster Upgrades Work on Amazon EKS

Follow cluster shop-prod from Kubernetes 1.35 to 1.36, then check yourself with 8 questions.

1Visual Walkthrough

Cluster shop-prod upgraded from Kubernetes 1.35 to 1.36 through the Amazon EKS API Left, Ana from the platform team and the shop-staging cluster, already on 1.36. An AWS account holds the Amazon EKS API, the support calendar for Kubernetes 1.35 with the upgrade policy, and upgrade insights for 1.36. Cluster shop-prod has its control plane, its cluster subnets, managed node group ng-general with three nodes, a Karpenter NodePool, Deployment catalog-sync, the kube-system add-ons and PodDisruptionBudget web. The walkthrough shows the support clock, checks before the upgrade, a control plane upgrade that needs free IPs, version skew, nodes and add-ons catching up, and rollback. Ana · platform AWS CLI · kubectl shop-staging Kubernetes 1.36 tries each version first AWS ACCOUNT 111122223333 · us-east-1 Amazon EKS API you start every upgrade here Kubernetes 1.35 on EKS Upgrade insights · for 1.36 refreshed every 24 hours CLUSTER shop-prod Control plane · run by AWS API server instances and etcd Cluster subnets · your VPC MANAGED NODE GROUP ng-general node-1 node-2 node-3 Karpenter NodePool default EC2NodeClass: alias al2023@latest Deployment catalog-sync Add-ons in kube-system PodDisruptionBudget web minAvailable 2 · 3 replicas

    2Quiz to check understanding

    Check yourself