Kubernetes is evolving into the operating system for the AI era, with new GKE Agent Sandbox, Dynamic Resource Allocation, and AI-powered GitOps operations leading the charge across the ecosystem.
Financial services organizations can now run PCI DSS workloads on shared-tenancy Amazon EKS without dedicated hosts - here's how to architect compliant Kubernetes infrastructure while balancing cost, security, and scalability.
AWS introduces session policies for EKS Pod Identity, enabling dynamic IAM permission scoping without creating additional roles—solving multi-tenant permission challenges.
AWS EKS introduces session policies for Pod Identity, enabling fine-grained IAM permission scoping without creating additional IAM roles.
EKS Hybrid Nodes lets you pair an AWS-managed control plane with on‑prem or edge worker nodes. Here’s what changes operationally, what doesn’t, and how to evaluate it against EKS Anywhere and plain upstream Kubernetes.
EKS Capabilities package Argo CD, AWS Controllers for Kubernetes (ACK), and Kube Resource Orchestrator (kro) as managed, Kubernetes-native building blocks. Here’s what changes when platform teams can compose AWS resources and Kubernetes resources behind custom APIs — without running the controllers themselves.
AWS is packaging common platform components (GitOps and infrastructure orchestration) as managed, Kubernetes-native ‘capabilities’ for Amazon EKS. Here’s what it changes for day-2 ops, how it compares to rolling your own controllers, and what to watch before you standardize on it.
AWS published a reference controller that connects Amazon Application Recovery Controller (ARC) zonal shifts to Karpenter node pools. Here’s what the integration changes operationally, how it works under the hood, and how to adopt it safely in production EKS.
AWS shows how to wire Amazon Application Recovery Controller’s zonal shift signals into Karpenter so clusters stop provisioning into a degraded AZ. Here’s why it matters, how it works, and what platform teams should standardize.
