Backend Connectivity Issues
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 190
- Forks
- 99
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 30
Description
I've been having issues with the Envoy Gateway and Ingress with cilium for some months now. I'm not sure if it's cilium's or envoy's fault, envoy logs "conntrack lookup failed: Success" on every request (it always returns an error because it does not receive a response from the backend) but it's just an info log.
My issue in cilium/cilium with infos etc.:
https://github.com/cilium/cilium/issues/29406
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 reviewing the Envoy Gateway and Ingress setup, the "conntrack lookup failed: Success" log, and the related cilium/cilium issue #29406. Reproduce the missing backend response and determine whether the failure belongs to Envoy or Cilium; done means the responsible component and a verified resolution are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100