Options for defining EKS Fargate Profiles.
|selectors||The selectors to match for pods to use this Fargate profile.|
|fargate||The name of the Fargate profile.|
|pod||The pod execution role to use for pods that match the selectors in the Fargate profile.|
|subnet||Select which subnets to launch your pods into.|
|vpc?||The VPC from which to select subnets to launch your pods into.|
The selectors to match for pods to use this Fargate profile.
Each selector must have an associated namespace. Optionally, you can also specify labels for a namespace.
At least one selector is required and you may specify up to five selectors.
(optional, default: generated)
The name of the Fargate profile.
(optional, default: a role will be automatically created)
The pod execution role to use for pods that match the selectors in the Fargate profile.
The pod execution role allows Fargate infrastructure to register with your cluster as a node, and it provides read access to Amazon ECR image repositories.
(optional, default: all private subnets of the VPC are selected.)
Select which subnets to launch your pods into.
At this time, pods running on Fargate are not assigned public IP addresses, so only private subnets (with no direct route to an Internet Gateway) are allowed.
(optional, default: all private subnets used by theEKS cluster)
The VPC from which to select subnets to launch your pods into.
By default, all private subnets are selected. You can customize this using