Back to all scenarios
Scenario #125
Networking
K8s v1.22, AWS EKS

High Latency in Inter-Namespace Communication

High latency observed in inter-namespace communication, leading to application timeouts.

Find this helpful?
What Happened

Pods in different namespaces experienced significant latency while trying to communicate, causing service timeouts.

Diagnosis Steps
  • 1Monitored network latency with kubectl and found inter-namespace traffic was unusually slow.
  • 2Checked network policies and discovered that overly restrictive policies were limiting traffic flow between namespaces.
Root Cause

Overly restrictive network policies blocking inter-namespace traffic.

Fix/Workaround
• Modified network policies to allow traffic between namespaces.
• Verified that latency reduced after policy changes.
Lessons Learned

Over-restrictive policies can cause performance issues.

How to Avoid
  • 1Apply network policies with careful consideration of cross-namespace communication needs.
  • 2Regularly review and update network policies.