EKS Fargate Profile Architecture

EKS Fargate Profile Architecture An architecture diagram generated by Archify. EKS control plane · Fargate scheduler · Architecture component EKS control plane Fargate scheduler Fargate profile · Selectors · execution role · Architecture component Fargate profile Selectors · execution role Selector 1 · namespace=default, env=fargate · Architecture component Selector 1 namespace=default, env=fargate Selector 2 · kube-system, k8s-app=kube-dns · Architecture component Selector 2 kube-system, k8s-app=kube-dns Fargate pods · One microVM per pod · Architecture component Fargate pods One microVM per pod evaluates match rule match rule placed on match Legend Frontend Cloud Security Message bus

How selectors work

  • • A pod matching both the profile's namespace and label selector is scheduled onto Fargate
  • • With only a namespace and no labels, every pod in that namespace matches
  • • If several profiles match, one is chosen arbitrarily, so design rules that do not overlap

Limitations

  • • DaemonSets, privileged containers, and HostNetwork or HostPort are unavailable
  • • GPUs and EBS volumes are unsupported, so use EFS for persistent volumes
  • • Pods land only in private subnets, and Classic Load Balancers are not supported

Operational tips

  • • A pod execution role is required before images can be pulled
  • • Requested CPU and memory round up to a Fargate size, so state resource requests precisely
  • • You skip node management, but pod startup is slower than on node groups