Skip to content

improve how dependency is defined between 'calico' and 'cluster' units

Thomas Morinrequested to merge
calico-cluster-dependency-improve into main

Calico is a particular component: because we need it early in the life of the mgmt cluster, the bootstrap cluster is deploying it on the mgmt cluster. The calico unit defined in the mgmt cluster, deploys only Flux definitions for Calico, which will allow to upgrade/update Calico on the mgmt cluster (on "day 2" operations).

Today the calico unit is declared with a "depends on" the cluster unit.

However, in the management cluster, the calico unit does not actually need the cluster unit (which contains only the Flux resources for the CAPI definition of the mgmt cluster that is applied after pivot). The calico unit could be applied at once, without waiting for the pivot to be done.

It's only in the bootstrap release of sylva-units that we need the calico unit (which deploys calico in the mgmt cluster) to depend on the cluster unit (which creates the management cluster).

Edited by Thomas Morin

Merge request reports