Read / Write Status: Read or Update the Status for a resource object. The Status can only changed through these update operations.
Worloads resources are responsible for managing and running your containers on the cluster. Containers are created +
Workloads resources are responsible for managing and running your containers on the cluster. Containers are created by Controllers through Pods. Pods run Containers and provide environmental dependencies such as shared or persistent storage Volumes and Configuration or Secret data injected into the container.
diff --git a/docs/api-reference/v1.6/index.html b/docs/api-reference/v1.6/index.html index 37d5d7f9c2..aa9b0133a8 100644 --- a/docs/api-reference/v1.6/index.html +++ b/docs/api-reference/v1.6/index.html @@ -74,7 +74,7 @@ notes on specific resource objects for details.Read / Write Status: Read or Update the Status for a resource object. The Status can only changed through these update operations.
Worloads resources are responsible for managing and running your containers on the cluster. Containers are created +
Workloads resources are responsible for managing and running your containers on the cluster. Containers are created by Controllers through Pods. Pods run Containers and provide environmental dependencies such as shared or persistent storage Volumes and Configuration or Secret data injected into the container.
diff --git a/docs/api-reference/v1.7/index.html b/docs/api-reference/v1.7/index.html index 575999d8cd..32f37051b1 100644 --- a/docs/api-reference/v1.7/index.html +++ b/docs/api-reference/v1.7/index.html @@ -74,7 +74,7 @@ notes on specific resource objects for details.Read / Write Status: Read or Update the Status for a resource object. The Status can only changed through these update operations.
Worloads resources are responsible for managing and running your containers on the cluster. Containers are created +
Workloads resources are responsible for managing and running your containers on the cluster. Containers are created by Controllers through Pods. Pods run Containers and provide environmental dependencies such as shared or persistent storage Volumes and Configuration or Secret data injected into the container.
diff --git a/docs/concepts/cluster-administration/manage-deployment.md b/docs/concepts/cluster-administration/manage-deployment.md index c89990c044..90fd1ea559 100644 --- a/docs/concepts/cluster-administration/manage-deployment.md +++ b/docs/concepts/cluster-administration/manage-deployment.md @@ -82,7 +82,7 @@ Because `kubectl` outputs resource names in the same syntax it accepts, it's eas ```shell $ kubectl get $(kubectl create -f docs/user-guide/nginx/ -o name | grep service) NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE -my-nginx-svc 10.0.0.208 80/TCP 0s +my-nginx-svc 10.0.0.208Worloads resources are responsible for managing and running your containers on the cluster. Containers are created +
Workloads resources are responsible for managing and running your containers on the cluster. Containers are created by Controllers through Pods. Pods run Containers and provide environmental dependencies such as shared or persistent storage Volumes and Configuration or Secret data injected into the container.
diff --git a/docs/resources-reference/v1.6/index.html b/docs/resources-reference/v1.6/index.html index 563418f892..fa2c13c0c9 100644 --- a/docs/resources-reference/v1.6/index.html +++ b/docs/resources-reference/v1.6/index.html @@ -15,7 +15,7 @@Worloads resources are responsible for managing and running your containers on the cluster. Containers are created +
Workloads resources are responsible for managing and running your containers on the cluster. Containers are created by Controllers through Pods. Pods run Containers and provide environmental dependencies such as shared or persistent storage Volumes and Configuration or Secret data injected into the container.
diff --git a/docs/resources-reference/v1.7/index.html b/docs/resources-reference/v1.7/index.html index da873a0724..9b6e230640 100644 --- a/docs/resources-reference/v1.7/index.html +++ b/docs/resources-reference/v1.7/index.html @@ -15,7 +15,7 @@Worloads resources are responsible for managing and running your containers on the cluster. Containers are created +
Workloads resources are responsible for managing and running your containers on the cluster. Containers are created by Controllers through Pods. Pods run Containers and provide environmental dependencies such as shared or persistent storage Volumes and Configuration or Secret data injected into the container.
diff --git a/docs/setup/independent/create-cluster-kubeadm.md b/docs/setup/independent/create-cluster-kubeadm.md index 5e24b6e892..0032b59c87 100644 --- a/docs/setup/independent/create-cluster-kubeadm.md +++ b/docs/setup/independent/create-cluster-kubeadm.md @@ -277,7 +277,9 @@ kubectl apply -f https://raw.githubusercontent.com/romana/romana/master/containe The official Weave Net set-up guide is [here](https://www.weave.works/docs/net/latest/kube-addon/). -**Note:** Weave Net works on `amd64`, `arm` and `arm64` without any extra action required. +**Note:** Weave Net works on `amd64`, `arm` and `arm64` without any extra action required. +Weave Net sets hairpin mode by default. This allows Pods to access themselves via their Service IP address +if they don't know their PodIP. ```shell export kubever=$(kubectl version | base64 | tr -d '\n') @@ -545,6 +547,12 @@ 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**. + 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 + add-on providers to get timely information about whether they support hairpin mode. 1. If you are using VirtualBox (directly or via Vagrant), you will need to ensure that `hostname -i` returns a routable IP address (i.e. one on the diff --git a/docs/setup/pick-right-solution.md b/docs/setup/pick-right-solution.md index 8a624c1523..01f17a1dd7 100644 --- a/docs/setup/pick-right-solution.md +++ b/docs/setup/pick-right-solution.md @@ -17,7 +17,7 @@ When you are ready to scale up to more machines and higher availability, a [host [Turnkey cloud solutions](#turnkey-cloud-solutions) require only a few commands to create and cover a wide range of cloud providers. -If you already have a way to configure hosting resources, use [kubeadm](/docs/getting-started-guides/kubeadm/) to easily bring up a cluster with a single command per machine. +If you already have a way to configure hosting resources, use [kubeadm](/docs/setup/independent/create-cluster-kubeadm/) to easily bring up a cluster with a single command per machine. [Custom solutions](#custom-solutions) vary from step-by-step instructions to general advice for setting up a Kubernetes cluster from scratch. @@ -88,7 +88,7 @@ If you are interested in supporting Kubernetes on a new platform, see ## Universal If you already have a way to configure hosting resources, use -[kubeadm](/docs/getting-started-guides/kubeadm/) to easily bring up a cluster +[kubeadm](/docs/setup/independent/create-cluster-kubeadm/) to easily bring up a cluster with a single command per machine. ## Cloud diff --git a/docs/tasks/configure-pod-container/configure-pod-configmap.md b/docs/tasks/configure-pod-container/configure-pod-configmap.md index d83790d943..7286accd9a 100644 --- a/docs/tasks/configure-pod-container/configure-pod-configmap.md +++ b/docs/tasks/configure-pod-container/configure-pod-configmap.md @@ -124,7 +124,7 @@ This page provides a series of usage examples demonstrating how to configure Pod SPECIAL_TYPE: charm ``` -1. Use `env-from` to define all of the ConfigMap's data as Pod environment variables. The key from the ConfigMap becomes the environment variable name in the Pod. +1. Use `envFrom` to define all of the ConfigMap's data as Pod environment variables. The key from the ConfigMap becomes the environment variable name in the Pod. ```yaml apiVersion: v1