Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add troubleshooting entry for extension is managing controllers #1942

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add troubleshooting entry for extension is managing controllers #1942

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
529ecb8
Add troubleshooting entry for `extension is managing controllers`
alpeb Mar 27, 2025
1307ee5
2.18
alpeb Apr 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions linkerd.io/content/2-edge/tasks/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1470,6 +1470,34 @@ NAME READY STATUS RESTARTS AGE
linkerd-service-mirror-7bb8ff5967-zg265 2/2 Running 0 50m
```

### √ extension is managing controllers {#l5d-multicluster-managed-controllers}

Example error:

```bash
‼ extension is managing controllers
* using legacy service mirror controller for Link: target
see https://linkerd.io/2/checks/#l5d-multicluster-managed-controllers for hints
```

In Linkerd `2.18` we introduced a declarative, GitOps-compatible approach to
establishing multicluster links. With this method, the controllers are
integrated into the multicluster extension, allowing you to supply the Link CR
and kubeconfig secrets manifests directly, without necessarily depending on the
`linkerd multicluster link` command. This differs from earlier versions of
Linkerd (pre-`v2.18`), where (in addition to the Link CR and secrets) controller
manifests needed to be provided each time a new link was created, requiring the
use of the `linkerd multicluster link` command — a process that was less suited
to a GitOps workflow.

This check ensures the linked clusters are using the new model. To migrate from
the old model, update the multicluster extension, referring your links into the
new `controllers` entry, as detailed in the [installing multicluster
doc](../installing-multicluster/#step-1-install-the-multicluster-control-plane).
The new controllers will be deployed, but they won't manage the links until the
old ones get deleted. Once the old ones are removed, the new controllers will
grab the Lease object allowing them to take over service mirroring.

### √ all gateway mirrors are healthy {#l5d-multicluster-gateways-endpoints}

Example errors:
Expand Down