~/ nmadiraju.com Amazon EKS · Managed node groups
arrow_back Back to nmadiraju
Visual Walkthrough · Amazon EKS compute

How Managed Node Groups Work on Amazon EKS

Follow node group ng-general from creation through a rolling AMI update, then check yourself with 8 questions.

1Visual Walkthrough

An EKS managed node group: its Auto Scaling group across two zones, the node role, and EKS Your VPC holds node group ng-general's Auto Scaling group across us-east-1a and us-east-1b, launched from a launch template with the EKS AL2023 AMI. EKS, run by AWS, holds the managed node group and the Kubernetes API server with the node role's access entry. The walkthrough shows nodes joining, a missing ECR permission, raising desired size, labels, and a rolling AMI update blocked and then unblocked by a PodDisruptionBudget. You aws eks · kubectl Launch template EKS AL2023 AMI Amazon ECR add-on images, e.g. the VPC CNI YOUR VPC · YOUR ACCOUNT ng-general · AUTO SCALING GROUP us-east-1a · 10.0.0.0/20 us-east-1b · 10.0.16.0/20 TERMINATED TERMINATED TERMINATED TERMINATED TERMINATED TERMINATED AMAZON EKS · RUN BY AWS Managed node group ng-general m6i.large · ON_DEMAND · maxUnavailable 1 Kubernetes API server access entry: ng-general-node-role type EC2_LINUX → group system:nodes created by EKS with the node group web: 4 Pods Pending 0/3 nodes are available: 3 Insufficient cpu PodDisruptionBudget pay IAM role ng-general-node-role used by the kubelet on every node

    2Quiz to check understanding

    Check yourself