kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update links to avoid redirects. (#5627) 

* Update links to avoid redirects.

* Fix double forward slash.
pull/5631/head
Steve Perry 2017-09-25 19:14:20 -07:00 committed by GitHub
parent 096fee2c39
commit cfa77d4670
8 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/concepts/containers/container-environment-variables.md
View File

@ -31,7 +31,7 @@ It is available through the `hostname` command or the
function call in libc. function call in libc.
The Pod name and namespace are available as environment variables through the 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, 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. as are any environment variables specified statically in the Docker image.

2
docs/concepts/storage/volumes.md
View File

@ -454,7 +454,7 @@ details.
A `downwardAPI` volume is used to make downward API data available to applications. 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. 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 ### projected

4
docs/concepts/workloads/controllers/petset.md
View File

@ -10,7 +10,7 @@ approvers:
title: PetSets 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 __This document has been deprecated__, but can still apply if you're using
Kubernetes version 1.4 or earlier. Kubernetes version 1.4 or earlier.
@ -227,7 +227,7 @@ web-1
A pet can piece together its own identity: 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 2. Run `hostname` to find its DNS name
3. Run `mount` or `df` to find its volumes (usually this is unnecessary) 3. Run `mount` or `df` to find its volumes (usually this is unnecessary)

2
docs/getting-started-guides/gce.md
View File

@ -202,7 +202,7 @@ field values:
IaaS Provider | Config. Mgmt | OS | Networking | Docs | Conforms | Support Level 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. For support level information on all solutions, see the [Table of solutions](/docs/getting-started-guides/#table-of-solutions) chart.

4
docs/getting-started-guides/scratch.md
View File

@ -91,7 +91,7 @@ to implement one of the above options:
- You can also write your own. - You can also write your own.
- **Compile support directly into Kubernetes** - **Compile support directly into Kubernetes**
- This can be done by implementing the "Routes" interface of a Cloud Provider module. - 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** - **Configure the network external to Kubernetes**
- This can be done by manually running commands, or through a set of externally maintained scripts. - 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. - 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 ### 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). [kubernetes-users group](https://groups.google.com/forum/#!forum/kubernetes-users), or come ask questions on [Slack](/docs/troubleshooting#slack).
## Support Level ## Support Level

2
docs/tasks/administer-cluster/calico-network-policy.md
View File

@ -15,7 +15,7 @@ This page shows how to use Calico for NetworkPolicy.
{% capture steps %} {% capture steps %}
## Deploying a cluster using Calico ## 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 ```shell
export NETWORK_POLICY_PROVIDER=calico export NETWORK_POLICY_PROVIDER=calico

2
docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
View File

@ -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. 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 [Heapster](https://github.com/kubernetes/heapster) monitoring needs to be deployed in the cluster
as Horizontal Pod Autoscaler uses it to collect metrics 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). heapster monitoring will be turned-on by default).
To specify multiple resource metrics for a Horizontal Pod Autoscaler, you must have a Kubernetes cluster To specify multiple resource metrics for a Horizontal Pod Autoscaler, you must have a Kubernetes cluster

2
docs/tutorials/index.md
View File

@ -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 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/) * [Example: WordPress and MySQL with Persistent Volumes](/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/)