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.

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

Multi-cluster demos using TrafficSplit object are not working #12769

Open
ValeriiVozniuk opened this issue Jun 24, 2024 · 2 comments
Open

Multi-cluster demos using TrafficSplit object are not working #12769

ValeriiVozniuk opened this issue Jun 24, 2024 · 2 comments
Assignees
Labels

Comments

@ValeriiVozniuk
Copy link

What is the issue?

Deploying multicluster demos from https://linkerd.io/2.15/tasks/multicluster/ and https://linkerd.io/2.15/tasks/automatic-failover/ results in non-working demos.

How can it be reproduced?

  1. Deploy all needed objects per "Multi-cluster communication" guide.
  2. At "Traffic Splitting" step, the TrafficSplit object is successfully created, but traffic is going only to west service/pod.
  3. Same for Failover test, the object is created, but commands shows that traffic staying in west.

Logs, error output, etc

  1. linkerd --context=west -n test viz stat trafficsplit
Error: error creating metrics request while making stats request: cannot find Kubernetes canonical name from friendly name [trafficsplit]
  1. No traffic in east
    image
  2. Same for Failover, no object for east in output
linkerd --context=west viz stat -n emojivoto svc --from deploy/vote-bot
NAME      MESHED   SUCCESS      RPS   LATENCY_P50   LATENCY_P95   LATENCY_P99   TCP_CONN
web-svc        -    80.65%   0.5rps           0ms           0ms           0ms          0
  1. The service mirror is working fine
k get svc -n emojivoto --context west
NAME           TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
emoji-svc      ClusterIP   10.43.88.215    <none>        8080/TCP,8801/TCP   66m
voting-svc     ClusterIP   10.43.151.134   <none>        8080/TCP,8801/TCP   66m
web-svc        ClusterIP   10.43.143.102   <none>        80/TCP              66m
web-svc-east   ClusterIP   10.43.36.204    <none>        80/TCP              65m

and curl requests are successfully routed to east pods via service

output of linkerd check -o short

linkerd check still produces garbled results

 Status check results are √
$ smi extension check
nning smi extension check                               / Running viz extension check
ension check                               - Running viz extension check
         \ Running viz extension check
nning viz extension check                               \ Running viz extension check
ension check                               | Running viz extension check
      / Running viz extension check
ng viz extension check                               / Running viz extension check
Running multicluster extension check                                        - Running multicluster extension check
                                   | Running multicluster extension check
Running multicluster extension check                                        / Running multicluster extension check
  Running multicluster extension check

For smi and multicluster it is a bit better

$ linkerd smi check --context=west
linkerd-smi
-----------
√ linkerd-smi extension Namespace exists
√ SMI extension service account exists
√ SMI extension pods are injected
√ SMI extension pods are running
√ SMI extension proxies are healthy

Status check results are √
$ linkerd multicluster check --context=west
linkerd-multicluster
--------------------
√ Link CRD exists
√ Link resources are valid
        * east
√ remote cluster access credentials are valid
        * east
√ clusters share trust anchors
        * east
√ service mirror controller has required permissions
        * east
√ service mirror controllers are running
        * east
√ probe services able to communicate with all gateway mirrors
        * east
√ all mirror services have endpoints
√ all mirror services are part of a Link
√ multicluster extension proxies are healthy
√ multicluster extension proxies are up-to-date
√ multicluster extension proxies and cli versions match

Status check results are √

Environment

Kubernetes version: v1.28.10+k3s1
Cluster Environment: oVirt
Host OS: Ubuntu 22.04 LTS
Linkerd version: edge-24.6.3

Possible solution

No response

Additional context

No response

Would you like to work on fixing this bug?

None

@kflynn
Copy link
Member

kflynn commented Jul 25, 2024

@ValeriiVozniuk Hey, sorry for the delay here! I'm going to try to sort this out in the next couple of days... 🤞

@xRTRx
Copy link

xRTRx commented Oct 22, 2024

Any updates?
Facing the same problem on linkerd edge-24.10.3
kubernetes version: v1.30.4
CNI: Cilium v1.15.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants