From 43021880befdfe1c8221fb971f08f950749a0f15 Mon Sep 17 00:00:00 2001 From: Chaminda Divitotawela Date: Tue, 11 Jun 2019 10:36:17 +1000 Subject: [PATCH] Update service.md (#14804) Removed one 'means' from incorrect repeat. --- content/en/docs/concepts/services-networking/service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index 69ba15fded..ad3344beff 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -253,7 +253,7 @@ Pod had failed and would automatically retry with a different backend Pod. You can use Pod [readiness probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes) to verify that backend Pods are working OK, so that kube-proxy in iptables mode -only sees backends that test out as healthy. Doing this means means you avoid +only sees backends that test out as healthy. Doing this means you avoid having traffic sent via kube-proxy to a Pod that's known to have failed. ![Services overview diagram for iptables proxy](/images/docs/services-iptables-overview.svg)