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

[Feature] Allow setting the name of the remote namespaces #2307

Closed
EladDolev opened this issue Jan 29, 2024 · 0 comments · Fixed by #2310
Closed

[Feature] Allow setting the name of the remote namespaces #2307

EladDolev opened this issue Jan 29, 2024 · 0 comments · Fixed by #2310

Comments

@EladDolev
Copy link
Contributor

Currently when offloading a local cluster to remote cluster, there are two supported methods. One method is with the EnforceSameName strategy, and the other is with the DefaultName which would create a randomally generated namespace

Assuming I got several clusters with offloaded namespaces that got the same name, I cannot use the EnforceSameName strategy

I'd like to have namespaces on the remote cluster with predetermined names, for several reasons

  • Namespaces names got meaning, for example when looking in K8s billing reports that are based on namespace
  • Having a "stable" name would allow to more easily offload/unoffload for fixing an issue, without having to change many other things that needs to be aware of the name of the namespace, and it would also make the billing reports stable
  • When able to control the names of the namespace, doing things programmatically is much easier

Thanks in advance and love your project ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant