From 21a2110f251c456d4b8422c9c97c014b2456948f Mon Sep 17 00:00:00 2001 From: eddytruyen Date: Sun, 24 Sep 2017 00:47:36 +0200 Subject: [PATCH] Update create-cluster-kubeadm.md --- docs/setup/independent/create-cluster-kubeadm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/setup/independent/create-cluster-kubeadm.md b/docs/setup/independent/create-cluster-kubeadm.md index 4f7c18f56f..0032b59c87 100644 --- a/docs/setup/independent/create-cluster-kubeadm.md +++ b/docs/setup/independent/create-cluster-kubeadm.md @@ -548,7 +548,7 @@ You may have trouble in the configuration if you see Pod statuses like `RunConta If not, you may still use the [NodePort feature of services](/docs/concepts/services-networking/service/#type-nodeport) or use `HostNetwork=true`. -1. **Pods cannot access themselves via their Service IP** +1. **Pods cannot access themselves via their Service IP**. Many network add-ons do not yet enable [hairpin mode](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/#a-pod-cannot-reach-itself-via-service-ip) which allows pods to access themselves via their Service IP if they don't know about their podIP. This is an issue related to [CNI](https://github.com/containernetworking/cni/issues/476). Please contact the providers of the network