Cluster API

Rationale

  • This POC of a baremetal cluster-api provider was started before the official cluster-api-provider-baremetal
  • This POC was relying on Airship Drydock/Maas. Thanks to the work done by the metal3.io team, most of content of this POC has become irrelevant.
  • The remaining questions that can be kind of answered by this POC are:
    • Is DivingBell still relevant. Is the cluster-api in charge of updating, rebooting machines when the machine specs are updated.
    • How much of Promenade is still relevant. cluster-api indeed helping to save the kubeadm token into configmaps to help machine to join.
    • Can kustomize be used to build the cluster-api MachineList and Cluster CRDs from Airship Site definitions.
This is not a "replacement" for airship drydock. This POC merely aims to highlight the potential advantages and pitfalls in going in that direction.

Lessons Learned

Baremetal machine greenfield deployment

  • TBD

Baremetal machine brownfield upgrade and update

  • Docker, Kubelet: TBD
  • OS: TBD

Kubernetes state maintenance

  • kubeproxy, api-server,…: TBD

Documentation

  • TBD

Associated GIT Repos