From 2adfb49ba9075902f1fcaa0cb2c53da0fa6c23f3 Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Thu, 6 Jul 2017 01:21:45 +0800 Subject: [PATCH] Update urls to 1.7 (#4276) * assign-pod-node.md * secret.md * kubernetes-objects.md * service.md --- docs/concepts/configuration/assign-pod-node.md | 2 +- docs/concepts/configuration/secret.md | 2 +- .../overview/working-with-objects/kubernetes-objects.md | 2 +- docs/concepts/services-networking/service.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/concepts/configuration/assign-pod-node.md b/docs/concepts/configuration/assign-pod-node.md index 900d7492bb..5cd997078d 100644 --- a/docs/concepts/configuration/assign-pod-node.md +++ b/docs/concepts/configuration/assign-pod-node.md @@ -222,7 +222,7 @@ marks that the node should not accept any pods that do not tolerate the taints. Tolerations are applied to pods, and allow (but do not require) the pods to schedule onto nodes with matching taints. -You add a taint to a node using [kubectl taint](/docs/user-guide/kubectl/v1.6/#taint). +You add a taint to a node using [kubectl taint](/docs/user-guide/kubectl/v1.7/#taint). For example, ```shell diff --git a/docs/concepts/configuration/secret.md b/docs/concepts/configuration/secret.md index 8cc6e34e14..bcfc3df241 100644 --- a/docs/concepts/configuration/secret.md +++ b/docs/concepts/configuration/secret.md @@ -124,7 +124,7 @@ The data field is a map. Its keys must match [`DNS_SUBDOMAIN`](https://git.k8s.io/community/contributors/design-proposals/identifiers.md), except that leading dots are also allowed. The values are arbitrary data, encoded using base64. -Create the secret using [`kubectl create`](/docs/user-guide/kubectl/v1.6/#create): +Create the secret using [`kubectl create`](/docs/user-guide/kubectl/v1.7/#create): ```shell $ kubectl create -f ./secret.yaml diff --git a/docs/concepts/overview/working-with-objects/kubernetes-objects.md b/docs/concepts/overview/working-with-objects/kubernetes-objects.md index 96629678dd..e5873ff105 100644 --- a/docs/concepts/overview/working-with-objects/kubernetes-objects.md +++ b/docs/concepts/overview/working-with-objects/kubernetes-objects.md @@ -40,7 +40,7 @@ Here's an example `.yaml` file that shows the required fields and object spec fo {% include code.html language="yaml" file="nginx-deployment.yaml" ghlink="/docs/concepts/overview/working-with-objects/nginx-deployment.yaml" %} -One way to create a Deployment using a `.yaml` file like the one above is to use the [`kubectl create`](/docs/user-guide/kubectl/v1.6/#create) command in the `kubectl` command-line interface, passing the `.yaml` file as an argument. Here's an example: +One way to create a Deployment using a `.yaml` file like the one above is to use the [`kubectl create`](/docs/user-guide/kubectl/v1.7/#create) command in the `kubectl` command-line interface, passing the `.yaml` file as an argument. Here's an example: ```shell $ kubectl create -f docs/user-guide/nginx-deployment.yaml --record diff --git a/docs/concepts/services-networking/service.md b/docs/concepts/services-networking/service.md index ef413898e0..d8deabb110 100644 --- a/docs/concepts/services-networking/service.md +++ b/docs/concepts/services-networking/service.md @@ -10,7 +10,7 @@ redirect_from: Kubernetes [`Pods`](/docs/user-guide/pods) are mortal. They are born and when they die, they are not resurrected. [`ReplicationControllers`](/docs/user-guide/replication-controller) in particular create and destroy `Pods` dynamically (e.g. when scaling up or down -or when doing [rolling updates](/docs/user-guide/kubectl/v1.6/#rolling-update)). While each `Pod` gets its own IP address, even +or when doing [rolling updates](/docs/user-guide/kubectl/v1.7/#rolling-update)). While each `Pod` gets its own IP address, even those IP addresses cannot be relied upon to be stable over time. This leads to a problem: if some set of `Pods` (let's call them backends) provides functionality to other `Pods` (let's call them frontends) inside the Kubernetes