From 63b8e39c5c2933cdb3f4f315e7dbc52d12599050 Mon Sep 17 00:00:00 2001 From: kairen Date: Wed, 27 Sep 2017 11:01:11 +0800 Subject: [PATCH 1/7] Link to using kubeadm page --- docs/setup/pick-right-solution.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 From 267c026201aa4483b5511ff7ddc3137dfa9bf353 Mon Sep 17 00:00:00 2001 From: chenhuan Date: Wed, 27 Sep 2017 14:40:52 +0800 Subject: [PATCH 2/7] fix the command output fix the command output --- docs/concepts/cluster-administration/manage-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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.208 80/TCP 0s ``` With the above commands, we first create resources under docs/user-guide/nginx/ and print the resources created with `-o name` output format From ed94d7351a6742eb6a79ec35fc798402b1af6ae2 Mon Sep 17 00:00:00 2001 From: Matt Brown Date: Wed, 27 Sep 2017 11:52:38 -0400 Subject: [PATCH 3/7] fix typo in api/resources reference: "Worloads" --- docs/api-reference/v1.5/index.html | 2 +- docs/api-reference/v1.6/index.html | 2 +- docs/api-reference/v1.7/index.html | 2 +- docs/resources-reference/v1.5/index.html | 2 +- docs/resources-reference/v1.6/index.html | 2 +- docs/resources-reference/v1.7/index.html | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/api-reference/v1.5/index.html b/docs/api-reference/v1.5/index.html index de6a3b57da..b7365b0e7c 100644 --- a/docs/api-reference/v1.5/index.html +++ b/docs/api-reference/v1.5/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.

WORKLOADS

-

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.

WORKLOADS

-

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.

WORKLOADS

-

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.5/index.html b/docs/resources-reference/v1.5/index.html index 186d452d46..36a50de98e 100644 --- a/docs/resources-reference/v1.5/index.html +++ b/docs/resources-reference/v1.5/index.html @@ -15,7 +15,7 @@
  • example

WORKLOADS

-

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.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 @@
  • example

WORKLOADS

-

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 @@
  • example

WORKLOADS

-

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.

From 45d92f805f8bff8f0f5f6a56e1c2722fb2737979 Mon Sep 17 00:00:00 2001 From: Sam Hagan Date: Tue, 26 Sep 2017 19:47:42 -0700 Subject: [PATCH 4/7] fix name typo in reference to deployment example --- docs/concepts/workloads/controllers/deployment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/workloads/controllers/deployment.md b/docs/concepts/workloads/controllers/deployment.md index 71379da9fa..862c190144 100644 --- a/docs/concepts/workloads/controllers/deployment.md +++ b/docs/concepts/workloads/controllers/deployment.md @@ -41,7 +41,7 @@ The following is an example of a Deployment. It creates a ReplicaSet to bring up In this example: -* A Deployment named `nginx` is created, indicated by the `metadata: name` field. +* A Deployment named `nginx-deployment` is created, indicated by the `metadata: name` field. * The Deployment creates three replicated Pods, indicated by the `replicas` field. * The Pod template's specification, or `template: spec` field, indicates that the Pods run one container, `nginx`, which runs the `nginx` @@ -137,7 +137,7 @@ The created ReplicaSet ensures that there are three `nginx` Pods running at all **Note:** Do not change this label. {: .note} -The `pod-template-hash label` is added by the Deployment controller to every ReplicaSet that a Deployment creates or adopts. +The `pod-template-hash label` is added by the Deployment controller to every ReplicaSet that a Deployment creates or adopts. This label ensures that child ReplicaSets of a Deployment do not overlap. It is generated by hashing the `PodTemplate` of the ReplicaSet and using the resulting hash as the label value that is added to the ReplicaSet selector, Pod template labels, and in any existing Pods that the ReplicaSet might have. From c5ebd07d8fd2d90974388a1e8dc15c651cc335c1 Mon Sep 17 00:00:00 2001 From: eddytruyen Date: Sun, 24 Sep 2017 00:37:42 +0200 Subject: [PATCH 5/7] Update create-cluster-kubeadm.md --- docs/setup/independent/create-cluster-kubeadm.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/setup/independent/create-cluster-kubeadm.md b/docs/setup/independent/create-cluster-kubeadm.md index 5e24b6e892..fbcf5b975b 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') @@ -606,6 +608,10 @@ kubectl -n ${NAMESPACE} describe pod ${POD_NAME} kubectl -n ${NAMESPACE} logs ${POD_NAME} -c ${CONTAINER_NAME} ``` +1. Many CNI-based network add-ons do not set [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. Please consult issue [containernetworking/cni#476](https://github.com/containernetworking/cni/issues/476) +for more up-to-date information or directly contact the providers of the network add-on providers to get +timely information about whether they support hairpin mode. {% endcapture %} From 9fb891b963eff099fec6e1cc3375c43cb778925b Mon Sep 17 00:00:00 2001 From: eddytruyen Date: Sun, 24 Sep 2017 00:45:38 +0200 Subject: [PATCH 6/7] Update create-cluster-kubeadm.md --- docs/setup/independent/create-cluster-kubeadm.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/setup/independent/create-cluster-kubeadm.md b/docs/setup/independent/create-cluster-kubeadm.md index fbcf5b975b..4f7c18f56f 100644 --- a/docs/setup/independent/create-cluster-kubeadm.md +++ b/docs/setup/independent/create-cluster-kubeadm.md @@ -547,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 @@ -608,10 +614,6 @@ kubectl -n ${NAMESPACE} describe pod ${POD_NAME} kubectl -n ${NAMESPACE} logs ${POD_NAME} -c ${CONTAINER_NAME} ``` -1. Many CNI-based network add-ons do not set [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. Please consult issue [containernetworking/cni#476](https://github.com/containernetworking/cni/issues/476) -for more up-to-date information or directly contact the providers of the network add-on providers to get -timely information about whether they support hairpin mode. {% endcapture %} From 21a2110f251c456d4b8422c9c97c014b2456948f Mon Sep 17 00:00:00 2001 From: eddytruyen Date: Sun, 24 Sep 2017 00:47:36 +0200 Subject: [PATCH 7/7] 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