RKE2: have Flux manage the lifecycle of calico and metallb
Today, we deploy calico and metallb as static Helm releases declared in RKE2ControlPlane, which does not give us a clean lifecycle (do we even have the ability to update those after the initial installation ?), and for sure does not give us a lifecycle consistent with the rest (based on Flux).
It will be important at some point to see what we can do about that, in particular to see if we could have Flux take over those components once the cluster is up.
Edited by Thomas Morin