Traffic from Linux Node to Windows Node does not get enriched by retina win pod
- Dominant language
- Go
- Stars
- 3.2k
- Forks
- 304
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 78
Description
**Describe the bug**
In a setup where retina is deployed on a windows node (PR being reviewed). A traffic is initiated between a client (on Linux Node) and server (on Windows node). The generated prom metrics do not generate namespace, pod information for the egress label from the Linux pod.
**Expected behavior**
Egress prom label should be configured.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Platform (please complete the following information):**
- OS: Windows
Contributor guide
Research direction
Start by reproducing the Linux-node client to Windows-node server setup described in the issue, with Retina deployed on a Windows node. Inspect the generated Prometheus metrics and compare the egress labels; the work is done when the Linux pod's namespace and pod information are present in the egress label.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- networking, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100