<p>I am using EKS Fargate and created a fargate profile based on this doc: <a href="https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html</a>.</p>
<p>In the doc it says Fargate is used to allocate what pods are deployed to Fargate instead of Nodegroup or EC2. So my question is should I always have one Fargate profile in one cluster? Is there any reason to have more than 1?</p>

<p>Consider that today Fargate profiles are immutable and they do not support wild-cards. So practically you end up using more than a Fargate profile when you have a rather dynamic environment and you want to selectively include/exclude namespaces / pod tags etc. There are other reasons why you <em>may</em> want to use different Fargate profiles for different namespaces in that the Fargate profile determines the network(s) your pods get deployed to and the execution IAM role of your pod (which you <em>could</em> use to selectively determine wich ECR private repo the pod can pull from). This role is not to be confused with the <a href="https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html" rel="nofollow noreferrer">IAM roles for SA</a>.</p>
