From 8d15eaa3b66f5f2f365c38df0f516b490d1996cb Mon Sep 17 00:00:00 2001 From: j-zimnowoda Date: Tue, 26 Nov 2019 06:31:10 +0100 Subject: [PATCH] Update debug-application.md (#17066) A Service has targetPort to indicated Pod's containerPort (service.spec.ports.targetPort) --- .../docs/tasks/debug-application-cluster/debug-application.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/debug-application-cluster/debug-application.md b/content/en/docs/tasks/debug-application-cluster/debug-application.md index c3b8afb6a7..053af8b654 100644 --- a/content/en/docs/tasks/debug-application-cluster/debug-application.md +++ b/content/en/docs/tasks/debug-application-cluster/debug-application.md @@ -177,7 +177,7 @@ If the list of pods matches expectations, but your endpoints are still empty, it have the right ports exposed. If your service has a `containerPort` specified, but the Pods that are selected don't have that port listed, then they won't be added to the endpoints list. -Verify that the pod's `containerPort` matches up with the Service's `containerPort` +Verify that the pod's `containerPort` matches up with the Service's `targetPort` #### Network traffic is not forwarded