From 45148c60e09af3653afdd7de0061f2f8fdd4abcd Mon Sep 17 00:00:00 2001 From: Chiranga Alwis Date: Mon, 15 Nov 2021 03:12:12 +0530 Subject: [PATCH] Review network policy ingress rules Add missing note to review Kubernetes Network Policy Ingress rules during debugging Kubernetes Service issues Update document link Co-authored-by: Qiming Teng --- .../docs/tasks/debug-application-cluster/debug-service.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/en/docs/tasks/debug-application-cluster/debug-service.md b/content/en/docs/tasks/debug-application-cluster/debug-service.md index 3b3b1c6081..4ff1a610b1 100644 --- a/content/en/docs/tasks/debug-application-cluster/debug-service.md +++ b/content/en/docs/tasks/debug-application-cluster/debug-service.md @@ -213,6 +213,13 @@ In order to highlight the full range of configuration, the Service you created here uses a different port number than the Pods. For many real-world Services, these values might be the same. +## Any Network Policy Ingress rules affecting the target Pods? + +If you have deployed any Network Policy Ingress rules which may affect incoming +traffic to `hostnames-*` Pods, these need to be reviewed. + +Please refer to [Network Policies](/docs/concepts/services-networking/network-policies/) for more details. + ## Does the Service work by DNS name? One of the most common ways that clients consume a Service is through a DNS