Open wongni opened 2 years ago
Adding to this - in a scenario where a management cluster has hundreds or thousands of workload clusters, we may run into scaling issues if all these capi/capc resources are in the eksa-system namespace. However, it sounds like breaking cluster resources into separate namespaces may have its own tradeoffs as well, since many operations in eks-a rely on the hardcoded eksa-system namespace and can add complexity, like clusterctl move
What would you like to be added: Currently, CAPI machines (k get machines -A) are created under
eksa-system
namespace. I want them to be under the namespace specified in the EKSA Cluster.For example,
In this case, CAPI machines are created uder
cluster-ns
instead ofeksa-system
Why is this needed:
I want to partition the clusters in the long-lived management cluster.