From cfa77d46707aba890cd04313292ebb824e5b7345 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Mon, 25 Sep 2017 19:14:20 -0700 Subject: [PATCH] Update links to avoid redirects. (#5627) * Update links to avoid redirects. * Fix double forward slash. --- docs/concepts/containers/container-environment-variables.md | 2 +- docs/concepts/storage/volumes.md | 2 +- docs/concepts/workloads/controllers/petset.md | 4 ++-- docs/getting-started-guides/gce.md | 2 +- docs/getting-started-guides/scratch.md | 4 ++-- docs/tasks/administer-cluster/calico-network-policy.md | 2 +- .../run-application/horizontal-pod-autoscale-walkthrough.md | 2 +- docs/tutorials/index.md | 2 +- 8 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/concepts/containers/container-environment-variables.md b/docs/concepts/containers/container-environment-variables.md index d5d0975cb7..513b09cb46 100644 --- a/docs/concepts/containers/container-environment-variables.md +++ b/docs/concepts/containers/container-environment-variables.md @@ -31,7 +31,7 @@ It is available through the `hostname` command or the function call in libc. The Pod name and namespace are available as environment variables through the -[downward API](/docs/tasks/configure-pod-container/downward-api-volume-expose-pod-information/). +[downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/). User defined environment variables from the Pod definition are also available to the Container, as are any environment variables specified statically in the Docker image. diff --git a/docs/concepts/storage/volumes.md b/docs/concepts/storage/volumes.md index baba44b07e..d919a01d09 100644 --- a/docs/concepts/storage/volumes.md +++ b/docs/concepts/storage/volumes.md @@ -454,7 +454,7 @@ details. A `downwardAPI` volume is used to make downward API data available to applications. It mounts a directory and writes the requested data in plain text files. -See the [`downwardAPI` volume example](/docs/tasks/configure-pod-container/downward-api-volume-expose-pod-information/) for more details. +See the [`downwardAPI` volume example](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) for more details. ### projected diff --git a/docs/concepts/workloads/controllers/petset.md b/docs/concepts/workloads/controllers/petset.md index 2ec7151d1b..48e6f6bd81 100644 --- a/docs/concepts/workloads/controllers/petset.md +++ b/docs/concepts/workloads/controllers/petset.md @@ -10,7 +10,7 @@ approvers: title: PetSets --- -__Warning:__ Starting in Kubernetes version 1.5, PetSet has been renamed to [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets). To use (or continue to use) PetSet in Kubernetes 1.5, you _must_ [migrate](/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set/) your existing PetSets to StatefulSets. For information on working with StatefulSet, see the tutorial on [how to run replicated stateful applications](/docs/tutorials/stateful-application/run-replicated-stateful-application). +__Warning:__ Starting in Kubernetes version 1.5, PetSet has been renamed to [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets). To use (or continue to use) PetSet in Kubernetes 1.5, you _must_ [migrate](/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set/) your existing PetSets to StatefulSets. For information on working with StatefulSet, see the tutorial on [how to run replicated stateful applications](/docs/tasks/run-application/run-replicated-stateful-application/). __This document has been deprecated__, but can still apply if you're using Kubernetes version 1.4 or earlier. @@ -227,7 +227,7 @@ web-1 A pet can piece together its own identity: -1. Use the [downward api](/docs/tasks/configure-pod-container/downward-api-volume-expose-pod-information/) to find its pod name +1. Use the [downward api](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/) to find its pod name 2. Run `hostname` to find its DNS name 3. Run `mount` or `df` to find its volumes (usually this is unnecessary) diff --git a/docs/getting-started-guides/gce.md b/docs/getting-started-guides/gce.md index 3598d7c46a..74823a8ee3 100644 --- a/docs/getting-started-guides/gce.md +++ b/docs/getting-started-guides/gce.md @@ -202,7 +202,7 @@ field values: IaaS Provider | Config. Mgmt | OS | Networking | Docs | Conforms | Support Level -------------------- | ------------ | ------ | ---------- | --------------------------------------------- | ---------| ---------------------------- -GCE | Saltstack | Debian | GCE | [docs](/docs/getting-started-guides/gce) | | Project +GCE | Saltstack | Debian | GCE | [docs](/docs/getting-started-guides/gce/) | | Project For support level information on all solutions, see the [Table of solutions](/docs/getting-started-guides/#table-of-solutions) chart. diff --git a/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md index 0e93a85301..43e0bc7db2 100644 --- a/docs/getting-started-guides/scratch.md +++ b/docs/getting-started-guides/scratch.md @@ -91,7 +91,7 @@ to implement one of the above options: - You can also write your own. - **Compile support directly into Kubernetes** - This can be done by implementing the "Routes" interface of a Cloud Provider module. - - The Google Compute Engine ([GCE](/docs/getting-started-guides/gce)/) and [AWS](/docs/getting-started-guides/aws/) guides use this approach. + - The Google Compute Engine ([GCE](/docs/getting-started-guides/gce/)/) and [AWS](/docs/getting-started-guides/aws/) guides use this approach. - **Configure the network external to Kubernetes** - This can be done by manually running commands, or through a set of externally maintained scripts. - You have to implement this yourself, but it can give you an extra degree of flexibility. @@ -896,7 +896,7 @@ pinging or SSH-ing from one node to another. ### Getting Help -If you run into trouble, please see the section on [troubleshooting](/docs/getting-started-guides/gce#troubleshooting), post to the +If you run into trouble, please see the section on [troubleshooting](/docs/getting-started-guides/gce/#troubleshooting), post to the [kubernetes-users group](https://groups.google.com/forum/#!forum/kubernetes-users), or come ask questions on [Slack](/docs/troubleshooting#slack). ## Support Level diff --git a/docs/tasks/administer-cluster/calico-network-policy.md b/docs/tasks/administer-cluster/calico-network-policy.md index 4543aa7069..424ffea4df 100644 --- a/docs/tasks/administer-cluster/calico-network-policy.md +++ b/docs/tasks/administer-cluster/calico-network-policy.md @@ -15,7 +15,7 @@ This page shows how to use Calico for NetworkPolicy. {% capture steps %} ## Deploying a cluster using Calico -You can deploy a cluster using Calico for network policy in the default [GCE deployment](/docs/getting-started-guides/gce) using the following set of commands: +You can deploy a cluster using Calico for network policy in the default [GCE deployment](/docs/getting-started-guides/gce/) using the following set of commands: ```shell export NETWORK_POLICY_PROVIDER=calico diff --git a/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md index 6d23d7d008..b13ea7a0ff 100644 --- a/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md +++ b/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md @@ -18,7 +18,7 @@ This document walks you through an example of enabling Horizontal Pod Autoscalin This example requires a running Kubernetes cluster and kubectl, version 1.2 or later. [Heapster](https://github.com/kubernetes/heapster) monitoring needs to be deployed in the cluster as Horizontal Pod Autoscaler uses it to collect metrics -(if you followed [getting started on GCE guide](/docs/getting-started-guides/gce), +(if you followed [getting started on GCE guide](/docs/getting-started-guides/gce/), heapster monitoring will be turned-on by default). To specify multiple resource metrics for a Horizontal Pod Autoscaler, you must have a Kubernetes cluster diff --git a/docs/tutorials/index.md b/docs/tutorials/index.md index e0a9b24d95..09c9ad91ea 100644 --- a/docs/tutorials/index.md +++ b/docs/tutorials/index.md @@ -31,7 +31,7 @@ each of which has a sequence of steps. * [Running a Single-Instance Stateful Application](/docs/tutorials/stateful-application/run-stateful-application/) -* [Running a Replicated Stateful Application](/docs/tutorials/stateful-application/run-replicated-stateful-application/) +* [Running a Replicated Stateful Application](/docs/tasks/run-application/run-replicated-stateful-application/) * [Example: WordPress and MySQL with Persistent Volumes](/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/)