in multi-cluster setup, probe services use the wrong port to check in version 2026.6.3
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
### What is the issue?
the same issue as https://github.com/linkerd/linkerd2/issues/14451 is happening to version 2026.6.3 as well
### How can it be reproduced?
fix it
### Logs, error output, etc
the same issue as https://github.com/linkerd/linkerd2/issues/14451 is happening to version 2026.6.3
### output of `linkerd check -o short`
the same issue as https://github.com/linkerd/linkerd2/issues/14451 is happening to version 2026.6.3
### Environment
the same issue as https://github.com/linkerd/linkerd2/issues/14451 is happening to version 2026.6.3
### Possible solution
_No response_
### Additional context
_No response_
### Would you like to work on fixing this bug?
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked issue 14451 and tracing how probe services select their ports in the multi-cluster setup. Reproduce the failure on version 2026.6.3; done when the probes check the intended port successfully in that setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100