Containers-roadmap: [EKS/Fargate] Support for Wildcard * Namespaces

[tabern]

the problem

Today you have to specify each namespace from which you want to run pods on Fargate in a Fargate profile.

the solution

EKS with Fargate will support adding wildcard * namespaces to the fargate profile

[apogrebnyak]

Will it support a * for any workspace, so we can have selective controls through labels only?

[rblaine95]

Will this allow us to have environment specific Fargate profiles?
For example:

• prod profile runs all pods in prod-* namespaces
• staging profile runs all pods in staging-* namespaces
• dev profile runs all pods in dev-* namespaces

[goraxe]

I would also suggest a list syntax dev,staging,prod . just as an example

[kirnberger1980]

We are running our apps in multitenancy model, which means, we e.g. have a multiple dev environments, which are running in separate namespaces:

myapp-dev2
...
myapp-devX

So in this case, it would be nice, if it is possible to define a profile with a wildcard.

myapp-dev*

So I prefer the solution of @rblaine95

[walkermundo]

We have the same setup as @kirnberger1980. So we would prefer @rblaine95's proposal too.

[Guillermogsjc]

Also, if you want for example to link a Gitlab CICD cluster using only fargate nodes, it has managed namespaces that match repository names ... so there is needed the wildcard to match any namespace orthogonally to the labels.