768 raises an important gap that we have currently. We should work towards improving the usability of MCM outside gardener context and also provide a local KIND based setup using which developers/adopters outside gardener can play around with MCM.
We should aim to achieve the following:
Choose any given infrastructure provider and setup MCM on the managed k8s that is provided out of the box from the provider or any k8s installation that is separately been setup on any infrastructure provider. This should also include the following (the list is not complete and needs to be enhanced as and when we find the gaps)
How and where to specify provider specific configurations (MachineClass example)
How to initialise nodes/VMs (either by doing what gardener does or by using kubeadm - to be explored)
[ ] #768
Update the documentation to provide how to build MCM docker image (out-of-tree) for a specific provider using provider-extensions.
Provide documentation on how to setup a KIND cluster with local provider and MCM.
Proposal to improve documentation across providers
How to categorize this issue?
/area control-plane /area dev-productivity /area usability /area documentation /kind enhancement /priority 3
What would you like to be added:
768 raises an important gap that we have currently. We should work towards improving the usability of MCM outside gardener context and also provide a local KIND based setup using which developers/adopters outside gardener can play around with MCM.
We should aim to achieve the following:
What should not be covered?
Why is this needed: To ease MCM adoption in the community