Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Namespace Support #21

Öffnen Sie
ezYakaEagle442 opened this issue Dec 13, 2022 · 3 comments
Öffnen Sie

Namespace Support #21

ezYakaEagle442 opened this issue Dec 13, 2022 · 3 comments
Labels
Enhancement New feature or request Needs Follow-up Additional information needed.

Kommentare

@ezYakaEagle442
Copy link

Is your feature request related to a problem? Please describe.

  • Teams A should be allowed to manage & access App A ONLY, not App B, App C neither
  • Teams B should be allowed to manage & access App B ONLY, not App A, App C neither
  • Teams C should be allowed to manage & access App C ONLY, not App A, App B neither

Describe the solution you'd like
This is the purpose of Namespaces in K8S.

Describe alternatives you've considered
The only other option would be to create a new ASA instance.

Additional context
see #20

@allxiao
Copy link
Member

allxiao commented Jan 20, 2023

We do not support namespace in ASA.

We would like to understand the customer's real scenarios, and we'll try to provide suggested solutions in the ASA world.

@allxiao allxiao added the Needs Follow-up Additional information needed. label Jan 20, 2023
@taoxu0903
Copy link

I believe the Team A/B/C RBAC control can be realized by app level RBAC. If so, is there any other motivation to have namespace-like feature in one ASA instance? if there is customer ask, what's the customer name and the motivation/customer impacct to ask for it?

@vmuthusamy-nlg
Copy link

Also, another problem is if Team A and B wants to work on App A, they cannot deploy their own versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Needs Follow-up Additional information needed.
Projects
None yet
Development

No branches or pull requests

4 participants