Decouple Infrastructure resource from machine controller #1129
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Milestone
/kind feature
Describe the solution you'd like
As a CAPI consumer I'd like to plug-in my own ControlPlane and Infrastructure resources [1] while still still reusing the existing machine controller implementation.
Today this is not possible because the machine/machinePool controllers are tightly coupled with the regular AzureCluster kind [2].
A scenario where this is handy is one where there's a common vision for a controlPlane across providers e.g cluster-api-provider-nested and the infrastructure management can differ arbitrarily from the core implementations, e.g BYO.
[1] https://github.com/kubernetes-sigs/cluster-api/blob/master/api/v1alpha4/cluster_types.go#L50-L58
[2] https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/master/controllers/azuremachine_controller.go#L186-L204
Anything else you would like to add:
Analogous to AWS
kubernetes-sigs/cluster-api-provider-aws#2125
kubernetes-sigs/cluster-api-provider-aws#2124
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: