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

[new feature] Support deploying the operator into a non-signadot namespace #15

Open
foxish opened this issue Jun 20, 2023 · 0 comments
Open

[new feature] Support deploying the operator into a non-signadot namespace #15

foxish opened this issue Jun 20, 2023 · 0 comments
Labels
platform

Comments

@foxish
Copy link
Member

foxish commented Jun 20, 2023

New feature or functionality
What would you like Signadot to do?

Currently, the Signadot Operator assumes that it is installed into the signadot namespace.
This item makes it possible to change that namespace into which it is installed in a cluster. This is primarily intended as a way to offer additional flexibility to operations teams that may have policies governing the naming / use of namespaces in a cluster.

Additional considerations
Anything in particular to think about regarding this new feature?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
platform
Projects
Signadot Public Roadmap
Status: Under Consideration
Milestone
No milestone
Development

No branches or pull requests
1 participant
@foxish