-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Open
Labels
Description
What is the issue?
The web page does not show the gateways for the multicluster connections that I already have. Here are the details

The gateways are already existing and the connectivity also works fine for the mirrored services
ubuntu@amp-node:~$ l version
Client version: edge-25.10.1
Server version: edge-25.10.1
ubuntu@amp-node:~$ l mc gateways
CLUSTER ALIVE NUM_SVC LATENCY
minipc-ha True 0 7ms
minipc-mkc True 3 7ms
ubuntu@amp-node:~$ k -n linkerd-multicluster get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
linkerd-gateway LoadBalancer 10.43.173.45 000.000.000.000 4143:31588/TCP,4191:31992/TCP 16d
probe-minipc-ha ClusterIP 10.43.248.82 <none> 4191/TCP 16d
probe-minipc-mkc ClusterIP 10.43.33.33 <none> 4191/TCP 16d
The annotations are also there, there was nothing changed manually[+] though[/+][-] thought[/-]
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{"linkerd.io/created-by":"linkerd/cli edge-25.10.1"},"labels":{"linkerd.io/extension":"multicluster","mirror.linkerd.io/cluster-name":"minipc-mkc","mirror.linkerd.io/mirrored-gateway":"true"},"name":"probe-minipc-mkc","namespace":"linkerd-multicluster"},"spec":{"ports":[{"name":"mc-probe","port":4191,"protocol":"TCP"}]}}
linkerd.io/created-by: linkerd/cli edge-25.10.1
creationTimestamp: "2025-10-04T05:39:35Z"
labels:
linkerd.io/extension: multicluster
mirror.linkerd.io/cluster-name: minipc-mkc
mirror.linkerd.io/mirrored-gateway: "true"
How can it be reproduced?
Create a multicluster setup with 1 mirror and then install the linkerd Viz
Logs, error output, etc
No errors, just the linkerd via web page does not show the gateways
output of linkerd check -o short
ubuntu@amp-node:~$ l check -o short
linkerd-version
---------------
‼ cli is up-to-date
is running version 25.10.1 but the latest edge version is 25.10.5
see https://linkerd.io/2/checks/#l5d-version-cli for hints
control-plane-version
---------------------
‼ control plane is up-to-date
is running version 25.10.1 but the latest edge version is 25.10.5
see https://linkerd.io/2/checks/#l5d-version-control for hints
linkerd-control-plane-proxy
---------------------------
‼ control plane proxies are up-to-date
some proxies are not running the current version:
* linkerd-destination-6b59f4555c-hqmzd (edge-25.10.1)
* linkerd-identity-8c59c94f-tcb8j (edge-25.10.1)
* linkerd-proxy-injector-7db6b4f55f-h66dc (edge-25.10.1)
see https://linkerd.io/2/checks/#l5d-cp-proxy-version for hints
linkerd-multicluster
--------------------
‼ multicluster extension proxies are up-to-date
some proxies are not running the current version:
* controller-minipc-ha-b65ff4d55-g57hk (edge-25.10.1)
* controller-minipc-mkc-649dc8f9c-ckkhc (edge-25.10.1)
* linkerd-gateway-568f77845b-g4smp (edge-25.10.1)
* linkerd-local-service-mirror-6d7496d5f5-dpntb (edge-25.10.1)
* controller-minipc-ha-b65ff4d55-g57hk (edge-25.10.1)
* controller-minipc-mkc-649dc8f9c-ckkhc (edge-25.10.1)
* linkerd-gateway-568f77845b-g4smp (edge-25.10.1)
* linkerd-local-service-mirror-6d7496d5f5-dpntb (edge-25.10.1)
see https://linkerd.io/2/checks/#l5d-multicluster-proxy-cp-version for hints
linkerd-viz
-----------
‼ viz extension proxies are up-to-date
some proxies are not running the current version:
* metrics-api-5dcb877b75-c4pt5 (edge-25.10.1)
* prometheus-55b99564c5-mcqmk (edge-25.10.1)
* tap-575b5967d-99vrr (edge-25.10.1)
* tap-injector-8648bbc76b-tqldw (edge-25.10.1)
* web-76d67d5b64-jr9zr (edge-25.10.1)
see https://linkerd.io/2/checks/#l5d-viz-proxy-cp-version for hints
Status check results are √
Environment
ubuntu@amp-node:~$ k version
Client Version: v1.31.4+k3s1
Kustomize Version: v5.4.2
Server Version: v1.31.4+k3s1
Ubuntu 24.04
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
None