Let metallb used in CAPD depend on calico only for kubeadm clusters

What does this MR do and why?

Has the CAPD used metallb unit depend on calico unit only for Kubeadm clusters.
It was otherwise failling with:

 ✗ Command timeout exceeded
Timed-out waiting for the following resources to be ready:
IDENTIFIER                                  STATUS     REASON        MESSAGE
HelmRelease/sylva-units-preview/sylva-units InProgress               HelmRelease generation is 1, but latest observed generation is -1
╰┄╴┬┄┄[Object conditions]
   ├┄╴Reconciling                           True       Progressing   Running 'install' action with timeout of 5m0s
   ├┄╴Ready                                 Unknown    Progressing   Running 'install' action with timeout of 5m0s
   ╰┄╴Released                              False      InstallFailed Helm install failed for release sylva-units-preview/sylva-units with chart sylva-units@0.0.0-git+9525021e46af.1: execution error at (sylva-units/templates/units.yaml:234:18): unit 'metallb' is declared with a dependency on disabled unit 'calico'

Related reference(s)

Test coverage

Merge request reports

Loading