<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>As of Aug 17th 2022, EKS now supports wildcards in Fargate Profile selectors. This means you can now run workloads from various Kubernetes namespaces with a single Fargate Profile.  Previously, you would have had to specify every namespace, and were limited to just 5 namespace selectors or label pairs.</p>
<p><a href="https://aws.amazon.com/about-aws/whats-new/2022/08/wildcard-support-amazon-eks-fargate-profile-selectors/" rel="nofollow noreferrer">https://aws.amazon.com/about-aws/whats-new/2022/08/wildcard-support-amazon-eks-fargate-profile-selectors/</a></p>
<p>For example, now you can use selectors like <code>*-staging</code> to match namespaces ending in <code>-staging</code>. You can also use <code>?</code> to match single characters. <code>app?</code> would match <code>appA</code> and <code>appB</code>.</p>
<pre><code>eksctl create fargateprofile \
    --cluster my-cluster \
    --name my-fargate-profile \
    --namespace *-staging
</code></pre>
