@@ -1470,6 +1470,34 @@ NAME READY STATUS RESTARTS AGE
14701470linkerd-service-mirror-7bb8ff5967-zg265 2/2 Running 0 50m
14711471` ` `
14721472
1473+ # ## √ extension is managing controllers {#l5d-multicluster-managed-controllers}
1474+
1475+ Example error:
1476+
1477+ ` ` ` bash
1478+ ‼ extension is managing controllers
1479+ * using legacy service mirror controller for Link: target
1480+ see https://linkerd.io/2/checks/# l5d-multicluster-managed-controllers for hints
1481+ ` ` `
1482+
1483+ In Linkerd ` 2.18` we introduced a declarative, GitOps-compatible approach to
1484+ establishing multicluster links. With this method, the controllers are
1485+ integrated into the multicluster extension, allowing you to supply the Link CR
1486+ and kubeconfig secrets manifests directly, without necessarily depending on the
1487+ ` linkerd multicluster link` command. This differs from earlier versions of
1488+ Linkerd (pre-` v2.18` ), where (in addition to the Link CR and secrets) controller
1489+ manifests needed to be provided each time a new link was created, requiring the
1490+ use of the ` linkerd multicluster link` command — a process that was less suited
1491+ to a GitOps workflow.
1492+
1493+ This check ensures the linked clusters are using the new model. To migrate from
1494+ the old model, update the multicluster extension, referring your links into the
1495+ new ` controllers` entry, as detailed in the [installing multicluster
1496+ doc](../installing-multicluster/# step-1-install-the-multicluster-control-plane).
1497+ The new controllers will be deployed, but they won' t manage the links until the
1498+ old ones get deleted. Once the old ones are removed, the new controllers will
1499+ grab the Lease object allowing them to take over service mirroring.
1500+
14731501### √ all gateway mirrors are healthy {#l5d-multicluster-gateways-endpoints}
14741502
14751503Example errors:
0 commit comments