argoproj / argoproj/argo-workflows
Multiple managed-namespace
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
With the [managed-namespace](https://argoproj.github.io/argo-workflows/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 👍.
Contributor guide
Research direction
Start with the managed-namespace installation documentation linked in the issue and trace the corresponding installation and namespace-management entry points. Determine how multiple namespaces would affect isolation and team ownership, then verify that the proposed behavior is documented and covered by appropriate tests; the linked pull request should also be reviewed for prior context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100