Stop Managing Kubernetes Infrastructure Manually — Use EKS Capabilities Instead

If you've ever spent hours wiring Helm charts, debugging IRSA roles, or babysitting controller upgrades in your Kubernetes cluster, this article is for you. I recently built a developer platform on Amazon EKS where a single YAML manifest creates a complete application stack — Kubernetes Deployment, Service, and an AWS SQS Queue — all managed through kubectl . No Terraform for the queue. No Helm chart for the controller. No controller pods eating cluster resources. The secret? EKS Capabilities — a GA feature (November 2025) that runs ACK and KRO as fully managed services on AWS infrastructure, outside your cluster. Here's exactly how I did it, including the RBAC gotcha that took me a while to figure out. What Are EKS Capabilities? Traditional approach: you install ACK controllers and KRO into your cluster using Helm. You manage versions, node resources, IRSA roles, and upgrades yourself. EKS Capabilities approach: AWS runs the controllers in their own accounts. You enable them with a si