This repository was archived by the owner on Oct 28, 2024. It is now read-only.
⚠️ Move controlplane.cluster.x-k8s.io components to controlplane/ #45
Assignees
Labels
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Milestone
Comments
|
/milestone v0.1.x |
|
/kind cleanup |
k8s-ci-robot
added
the
kind/cleanup
|
/assign |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When we look at other CAPI implementations instead of using
multi-groupcontrollers they typically are deployed as independent controllers, they're even built this way, for example see kcp incontrolplane/kubeadm/in https://github.com/kubernetes-sigs/cluster-ap while the main typesNestedClusterin our world live usually at the top level, eg https://github.com/kubernetes-sigs/cluster-api-provider-aws you can even see theekscontrolplane is built incontrolplane/eks/https://github.com/kubernetes-sigs/cluster-api-provider-aws/tree/main/controlplane/eks.We should adjust to having the 4
controlplanegroup's resources incontrolplane/nested/and have only the top levelNestedClusterat/this will also make it easier to co-operate if we eventually transition to kcp (eg #44)The text was updated successfully, but these errors were encountered: