TechOps Examples

Hey — It's Govardhana MK 👋

Welcome to another technical edition.

Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.

Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities, and articles.

👋 👋 A big thank you to today's sponsor MINTLIFY

Mintlify helps you create fast, beautiful docs that developers actually enjoy using. Write in markdown, sync with your repo, and deploy in minutes. Built-in components handle search, navigation, API references, and interactive examples out of the box, so you can focus on clear content instead of custom infrastructure.

Automatic versioning, analytics, and AI powered search make it easy to scale as your product grows. Your docs stay accurate automatically with AI-powered workflows with every pull request.

Whether you're a dev, technical writer, part of devrel, and beyond, Mintlify fits into the way you already work and helps your documentation keep pace with your product.

Get Started for Free Today

Powered by: Jobsurface.com

Browse 727 Worldwide Jobs Here →

Looking to promote your company, product, service, or event to 48,000+ Cloud Native Professionals? Let's work together. Advertise With Us

Running Kubernetes on AWS has always required two separate engineering disciplines. The first is Kubernetes itself: workload configuration, networking policies, RBAC, autoscaling. The second is the underlying AWS infrastructure: EC2 instance selection, Auto Scaling Groups, launch templates, EBS CSI drivers, VPC CNI configuration, load balancer controllers, node group updates. Most teams underestimate how much operational burden lives in that second category until they are six months into a production cluster and spending more engineering time on node upgrades and driver compatibility than on the applications they are supposed to be shipping.

EKS Auto Mode is AWS's answer to this split. It absorbs the infrastructure management layer entirely, leaving your team responsible only for the Kubernetes workload layer.

EKS Auto Mode is a cluster operating mode introduced by AWS that fully manages the compute, storage, and networking infrastructure of an EKS cluster on your behalf. When you enable Auto Mode, AWS takes over node provisioning, node lifecycle management, driver installation, Kubernetes version compatibility, security patching, and the core add-ons that standard clusters require you to manage manually.

The key distinction is ownership. In a standard EKS cluster, you own the nodes. You decide the instance types, you manage the node groups, you install and upgrade the VPC CNI plugin, the EBS CSI driver, CoreDNS, kube-proxy, and the AWS Load Balancer Controller. When a new Kubernetes version ships, you coordinate the upgrade across all of these components. When a CVE hits the AMI, you roll the nodes.

In Auto Mode, AWS owns all of that. You deploy workloads. AWS ensures the infrastructure underneath runs them.

When a pod is created and enters Pending state because no node has capacity, the Auto Mode controller built into the EKS control plane triggers node provisioning. This is Karpenter running as a managed component inside the control plane itself, not as a deployment you install and maintain in your cluster.

Karpenter evaluates the pod's resource requests, node selectors, tolerations, and topology spread constraints. It then calls the EC2 Fleet API requesting instances from a set of compatible families. Auto Mode uses Spot instances by default where appropriate and falls back to On-demand. The instance selection is optimized for bin-packing: finding the instance that fits the pending workload with the least wasted capacity.

The node that boots runs an AWS optimized AMI that includes the VPC CNI plugin, EBS CSI driver, kubelet, and kube-proxy pre installed at versions that are guaranteed compatible with your cluster's Kubernetes version. You never see this node as a managed node group in the EC2 console in the same way. It appears as an EC2 instance tagged to your cluster, but its lifecycle is owned entirely by EKS Auto Mode.

Nodes have a maximum age enforced by Auto Mode. Before a node reaches the configured maximum age (default 21 days), Auto Mode drains it and replaces it with a fresh instance running the latest patched AMI. This rotation happens automatically without operator intervention. It is also what gives you continuous security patch delivery without maintenance windows.

🔴 Get my DevOps & Kubernetes ebooks! (free for Premium Club and Personal Tier newsletter subscribers)