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.

Sign up for GitHub

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

Jump to bottom

Ambassador Operator Should Support Multiple Ambassador deployments in the same namespace #60

Open
iNoahNothing opened this issue Jul 21, 2020 · 0 comments
Open

Ambassador Operator Should Support Multiple Ambassador deployments in the same namespace #60

iNoahNothing opened this issue Jul 21, 2020 · 0 comments
Labels
t:feature New feature or request

Comments

@iNoahNothing
Copy link

A very common usecase is to deploy multiple Ambassadors for different use cases.

This is only allowed in the current iteration of the operator using separate namespaces. This should be changed to allow for all deployments to be in the ambassador namespace
@iNoahNothing iNoahNothing added the t:feature New feature or request label Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
t:feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iNoahNothing