From 90650aca2efd056fa3cf64da1604bcc0a0b3c83f Mon Sep 17 00:00:00 2001 From: cmluciano Date: Thu, 19 Oct 2017 12:48:43 -0400 Subject: [PATCH] Document HostPort configuration for CNI plugins with kubeadm (#5940) --- docs/setup/independent/create-cluster-kubeadm.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/docs/setup/independent/create-cluster-kubeadm.md b/docs/setup/independent/create-cluster-kubeadm.md index 8a67b6603b..34fc90de6a 100644 --- a/docs/setup/independent/create-cluster-kubeadm.md +++ b/docs/setup/independent/create-cluster-kubeadm.md @@ -555,11 +555,14 @@ You may have trouble in the configuration if you see Pod statuses like `RunConta 1. **I tried to set `HostPort` on one workload, but it didn't have any effect**. The `HostPort` and `HostIP` functionality is available depending on your Pod Network - provider. Please contact the author of the Pod Network solution to find out whether - `HostPort` and `HostIP` functionality are available. - - If not, you may still use the [NodePort feature of - services](/docs/concepts/services-networking/service/#type-nodeport) or use `HostNetwork=true`. + provider. + + - Verified HostPort CNI providers: + - Calico + - Canal + - Flannel + - [CNI portmap Documentation](https://github.com/containernetworking/plugins/blob/master/plugins/meta/portmap/README.md) + - If your network provider does not support the portmap CNI plugin, you may need to use a [service of type NodePort](/docs/concepts/services-networking/service/#type-nodeport) or use `HostNetwork=true`. 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)