DataDog
User Issue: Egress Network Disruption for Inter Cluster in K8's not working
Describe the bug I did 3 experiments for doing a delay of packets for K8's services in 2 different clusters by using hosts. The one with ingress flow worked but the one without any flow and egress didn't work as expected. Basically no latency was seen when default or egress was used. Everything with 3 experiments were same except for either flow was not mention as it's optional (default case and no latency seen) or flow was set to either egress (no latency seen) or ingress (latency seen).
To Reproduce Steps to reproduce the behavior: Do a network delay test in Inter-Cluster in K8 with flow field empty or with flow set to egress.
Expected behavior Network delay should have happened to egress flow as well.
Screenshots If applicable, add screenshots to help explain your problem.
Egress or Default flow with no latency seen:
Ingress flow with latency see
Environment:
- Kubernetes version: 1.28
- Controller version: 10.7.0
- Cloud provider (or local): aws
- Base OS for Kubernetes: amazon linux
Additional context N/A
