argo-workflows icon indicating copy to clipboard operation
argo-workflows copied to clipboard

Multiple managed-namespace

Open guillaumBrisard opened this issue 4 years ago • 4 comments

Summary

With the managed-namespace installation, would it be possible to manage multiple namespaces ?

Use Cases

On a single cluster, I have differents teams and each one of them handle multiple products. And I would want each team to handle her own argo workflow installation for multiple products. Because one install by product is to heavy, and with a cluster install there is no enough isolation.


Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

guillaumBrisard avatar Sep 20 '21 09:09 guillaumBrisard

How about we manage namespaces based on labels?

kind: Namespace
metadata:
  name: my-ns
  labels:
    workflows.argoproj.io/managed-namespace: "true"

alexec avatar Feb 07 '22 17:02 alexec

It's not enough I think. When we have 2 argo workflow deployed on the same cluster. We will need to specify which one we want to use for ours workflows.

To manage namespace there is 2 options :

  1. the managed namespace decide which argo wf namespace it will use
  2. the argo wf ns decide the list of ns it will manage

The 2 options are not exclusive, but I will need to control which ns used my argo wf ns. With a white list for example.

guillaumBrisard avatar Feb 21 '22 12:02 guillaumBrisard

I think this can also be achieved by using instance ID.

alexec avatar Feb 21 '22 16:02 alexec

my current thinking is cluster admin defines team1 with namespace1/serviceaccount1/rolebinding1/gitrepo1, and defines team2 with namespace2/serviceaccount2/rolebinding2/gitrepo2. But what prevents team2 from creating a workflow yaml that references namespace1/serviceaccount1 ?

tooptoop4 avatar Jul 23 '22 09:07 tooptoop4

Is there any updates on this issue? Looks like it's been stale for a while.

evgeniy-khatko avatar May 24 '23 05:05 evgeniy-khatko