Implement VIP-based Kubernetes API exposure instead of using MaaS DNS in Cluster API MaaS provider

[Frantche]

---

name: Implement VIP-based Kubernetes API exposure instead of using MaaS DNS in Cluster API MaaS provider

Version
cluster-api-provider-maas: v0.4.0
MaaS: 3.2.8

The Problem To Be Solved

In our current setup, the provisioning and configuration of machines in the MaaS infrastructure are managed by a separate team. However, during the deployment process in the Cluster API MaaS provider, the operator tries to update MaaS' DNS, which is restricted due to our limited permissions

Possible Solution

Implement a solution to avoid using the MaaS DNS for exposing the Kubernetes API and instead utilize a Virtual IP (VIP) approach for improved flexibility and high availability. The VIP can be configured using KeepAlived in the bootstrap.

[stefanSpectro]

Can this be looked at?

Not having apiserver operate in HA via a VIP seems to cause apiserver accessibility issues during sequential repave of control plane nodes.

Or can we at least get a clear explanation as to why this is not supported/possible/going to be implemented?

@spectrocloud/palette-pcp