Closed christopherhein closed 3 years ago
When we look at other CAPI implementations instead of using multi-group controllers they typically are deployed as independent controllers, they're even built this way, for example see kcp in controlplane/kubeadm/ in https://github.com/kubernetes-sigs/cluster-ap while the main types NestedCluster in our world live usually at the top level, eg https://github.com/kubernetes-sigs/cluster-api-provider-aws you can even see the eks controlplane is built in controlplane/eks/ https://github.com/kubernetes-sigs/cluster-api-provider-aws/tree/main/controlplane/eks.
multi-group
controlplane/kubeadm/
NestedCluster
eks
controlplane/eks/
We should adjust to having the 4 controlplane group's resources in controlplane/nested/ and have only the top level NestedCluster at / this will also make it easier to co-operate if we eventually transition to kcp (eg #44)
controlplane
controlplane/nested/
/
/milestone v0.1.x
/kind cleanup
/assign
When we look at other CAPI implementations instead of using
multi-group
controllers 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 typesNestedCluster
in our world live usually at the top level, eg https://github.com/kubernetes-sigs/cluster-api-provider-aws you can even see theeks
controlplane is built incontrolplane/eks/
https://github.com/kubernetes-sigs/cluster-api-provider-aws/tree/main/controlplane/eks.We should adjust to having the 4
controlplane
group's resources incontrolplane/nested/
and have only the top levelNestedCluster
at/
this will also make it easier to co-operate if we eventually transition to kcp (eg #44)