Test how linkerd and cillium interact
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
Based on https://github.com/linkerd/linkerd2/issues/6238#issuecomment-858089072 and https://github.com/linkerd/linkerd2/issues/6238#issuecomment-858796177, it appears that there may be issues between linkerd proxies and Cillium's load balancing features. In order to get a better understanding on what these issues are and possibly how we can fix them, we should write new integration tests that exercise running Linkerd with Cillium.
We should make sure that some of the following features work in a cillium environment:
- gRPC load balancing
- service profiles
- destination resolution
There may be other issues like multicluster but that might be out of scope for these tests.
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 discussion in linkerd2 issue 6238, especially comments 858089072 and 858796177, to understand the reported proxy and Cilium load-balancing interactions. Identify the repository's integration-test entry point, then cover gRPC load balancing, service profiles, and destination resolution in a Cilium environment. Done means these scenarios have reproducible integration coverage; multicluster is explicitly out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, kubernetes
- Domain
- distributed-systems, networking, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100