One of the kubeadm goals was to provide a toolbox for higher-level tools.

However, as of today, kubeadm can be consumed only as a CLI command, and this limits the options for higher-level tools when designing kubeadm integration; the current model is also a limitation because the func existing in kubeadm e.g. for managing certificates, kubeconfig, or the kubeadm API can't be re-used (e.g. CAPI is re-implementing some of this functions)

This issue is about collecting ideas about which shape the library should take, and define a viable path to get the library in place.