You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ❤️
The text was updated successfully, but these errors were encountered:
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 theDefaultName
which would create a randomally generated namespaceAssuming I got several clusters with offloaded namespaces that got the same name, I cannot use the
EnforceSameName
strategyI'd like to have namespaces on the remote cluster with predetermined names, for several reasons
Thanks in advance and love your project ❤️
The text was updated successfully, but these errors were encountered: