Setting the file. One moment.
Subchapter 31.9
references/eks-auto-mode.mdMarkdown4 KBView on GitHub
EKS Auto Mode extends AWS management of Kubernetes clusters beyond the cluster itself, to allow AWS to also set up and manage the infrastructure that enables the smooth operation of your workloads. You can delegate key infrastructure decisions and leverage the expertise of AWS for day-to-day operations. Cluster infrastructure managed by AWS includes many Kubernetes capabilities as core components, as opposed to add-ons, such as compute autoscaling, pod and service networking, application load balancing, cluster DNS, block storage, and GPU support.
In general it is critical to avoid making assumptions about EKS Auto Mode clusters, their capabilities and how to configure them relative to traditional EKS clusters. The EKS Auto Mode documentation should be referred to as much as needed to make informed decisions.
EKS Auto Mode relies on Karpenter autoscaling to provision and manage cluster compute, and nodes are designed to be treated like appliances. EKS Auto Mode does the following:
Amazon EKS Node Classes are templates that offer granular control over the configuration of your EKS Auto Mode managed nodes. A Node Class defines infrastructure-level settings that apply to groups of nodes in your EKS cluster, including network configuration, storage settings, and resource tagging.
EKS Auto Mode uses a node class CRD that is different from standard Karpenter. You must refer to the relevant EKS Auto Mode documentation (opens in a new tab) when answering questions or authoring configurations related to Auto Mode node classes.
Amazon EKS node pools offer a flexible way to manage compute resources in your Kubernetes cluster. This topic demonstrates how to create and configure node pools by using Karpenter, a node provisioning tool that helps optimize cluster scaling and resource utilization. With Karpenter’s NodePool resource, you can define specific requirements for your compute resources, including instance types, availability zones, architectures, and capacity types.
EKS Auto Mode uses different labels than Karpenter. Labels related to EC2 managed instances start with eks.amazonaws.com.
See the relevant documentation (opens in a new tab) for more information on EKS Auto Mode node pools.
EKS Auto Mode has some networking capabilities that differ from standard EKS clusters.
EKS Auto Mode creates and configures Application Load Balancers (ALBs). For example, EKS Auto Mode creates a load balancer when you create an Ingress Kubernetes object and configures it to route traffic to your cluster workload.
This works much the same way as the AWS Load Balancer Controller but is a different implementation. Key differences include:
TargetGroupBinding and IngressClassParams CRDs have different signatures, see the documentation for details.See the documentation (opens in a new tab) for more information.
EKS Auto Mode supports the following through network policies:
See the documentation (opens in a new tab) for more information.