whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix broken link target

Browse Source
This commit is contained in:
Bin Liu
2017-12-21 16:13:15 +08:00
committed by bin liu
parent 0f0ccd13b0
commit fc524bd7e3
6 changed files with 25 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/configuration/manage-compute-resources-container.md
+2 -2
View File
@@ -239,7 +239,7 @@ the node.
The amount of resources available to Pods is less than the node capacity, because The amount of resources available to Pods is less than the node capacity, because
system daemons use a portion of the available resources. The `allocatable` field system daemons use a portion of the available resources. The `allocatable` field
[NodeStatus](/docs/resources-reference/{{page.version}}/#nodestatus-v1-core) [NodeStatus](/docs/api-reference/{{page.version}}/#nodestatus-v1-core)
gives the amount of resources that are available to Pods. For more information, see gives the amount of resources that are available to Pods. For more information, see
[Node Allocatable Resources](https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md). [Node Allocatable Resources](https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md).
@@ -570,7 +570,7 @@ consistency across providers and platforms.
* [Container](/docs/api-reference/{{page.version}}/#container-v1-core) * [Container](/docs/api-reference/{{page.version}}/#container-v1-core)
* [ResourceRequirements](/docs/resources-reference/{{page.version}}/#resourcerequirements-v1-core) * [ResourceRequirements](/docs/api-reference/{{page.version}}/#resourcerequirements-v1-core)
{% endcapture %} {% endcapture %}
docs/concepts/workloads/pods/disruptions.md
+1 -1
View File
@@ -131,7 +131,7 @@ during application updates is configured in the controller spec.
(Learn about [updating a deployment](/docs/concepts/workloads/controllers/deployment/#updating-a-deployment).) (Learn about [updating a deployment](/docs/concepts/workloads/controllers/deployment/#updating-a-deployment).)
When a pod is evicted using the eviction API, it is gracefully terminated (see When a pod is evicted using the eviction API, it is gracefully terminated (see
`terminationGracePeriodSeconds` in [PodSpec](/docs/resources-reference/{{page.version}}/#podspec-v1-core).) `terminationGracePeriodSeconds` in [PodSpec](/docs/api-reference/{{page.version}}/#podspec-v1-core).)
## PDB Example ## PDB Example
docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md
+3 -3
View File
@@ -85,9 +85,9 @@ unless the Pod's grace period expires. For more details, see
### Reference ### Reference
* [Lifecycle](/docs/resources-reference/{{page.version}}/#lifecycle-v1-core) * [Lifecycle](/docs/api-reference/{{page.version}}/#lifecycle-v1-core)
* [Container](/docs/resources-reference/{{page.version}}/#container-v1-core) * [Container](/docs/api-reference/{{page.version}}/#container-v1-core)
* See `terminationGracePeriodSeconds` in [PodSpec](/docs/resources-reference/{{page.version}}/#podspec-v1-core) * See `terminationGracePeriodSeconds` in [PodSpec](/docs/api-reference/{{page.version}}/#podspec-v1-core)
{% endcapture %} {% endcapture %}
docs/tasks/configure-pod-container/configure-persistent-volume-storage.md
+4 -4
View File
@@ -200,10 +200,10 @@ PersistentVolume are not present on the Pod resource itself.
### Reference ### Reference
* [PersistentVolume](/docs/resources-reference/{{page.version}}/#persistentvolume-v1-core) * [PersistentVolume](/docs/api-reference/{{page.version}}/#persistentvolume-v1-core)
* [PersistentVolumeSpec](/docs/resources-reference/{{page.version}}/#persistentvolumespec-v1-core) * [PersistentVolumeSpec](/docs/api-reference/{{page.version}}/#persistentvolumespec-v1-core)
* [PersistentVolumeClaim](/docs/resources-reference/{{page.version}}/#persistentvolumeclaim-v1-core) * [PersistentVolumeClaim](/docs/api-reference/{{page.version}}/#persistentvolumeclaim-v1-core)
* [PersistentVolumeClaimSpec](/docs/resources-reference/{{page.version}}/#persistentvolumeclaimspec-v1-core) * [PersistentVolumeClaimSpec](/docs/api-reference/{{page.version}}/#persistentvolumeclaimspec-v1-core)
{% endcapture %} {% endcapture %}
docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md
+6 -6
View File
@@ -40,7 +40,7 @@ In the configuration file, you can see that the Pod has a `downwardAPI` Volume,
and the Container mounts the Volume at `/etc`. and the Container mounts the Volume at `/etc`.
Look at the `items` array under `downwardAPI`. Each element of the array is a Look at the `items` array under `downwardAPI`. Each element of the array is a
[DownwardAPIVolumeFile](/docs/resources-reference/{{page.version}}/#downwardapivolumefile-v1-core). [DownwardAPIVolumeFile](/docs/api-reference/{{page.version}}/#downwardapivolumefile-v1-core).
The first element specifies that the value of the Pod's The first element specifies that the value of the Pod's
`metadata.labels` field should be stored in a file named `labels`. `metadata.labels` field should be stored in a file named `labels`.
The second element specifies that the value of the Pod's `annotations` The second element specifies that the value of the Pod's `annotations`
@@ -234,11 +234,11 @@ inject the Pod's name into the well-known environment variable.
{% capture whatsnext %} {% capture whatsnext %}
* [PodSpec](/docs/resources-reference/{{page.version}}/#podspec-v1-core) * [PodSpec](/docs/api-reference/{{page.version}}/#podspec-v1-core)
* [Volume](/docs/resources-reference/{{page.version}}/#volume-v1-core) * [Volume](/docs/api-reference/{{page.version}}/#volume-v1-core)
* [DownwardAPIVolumeSource](/docs/resources-reference/{{page.version}}/#downwardapivolumesource-v1-core) * [DownwardAPIVolumeSource](/docs/api-reference/{{page.version}}/#downwardapivolumesource-v1-core)
* [DownwardAPIVolumeFile](/docs/resources-reference/{{page.version}}/#downwardapivolumefile-v1-core) * [DownwardAPIVolumeFile](/docs/api-reference/{{page.version}}/#downwardapivolumefile-v1-core)
* [ResourceFieldSelector](/docs/resources-reference/{{page.version}}/#resourcefieldselector-v1-core) * [ResourceFieldSelector](/docs/api-reference/{{page.version}}/#resourcefieldselector-v1-core)
{% endcapture %} {% endcapture %}
docs/tasks/inject-data-application/environment-variable-expose-pod-information.md
+9 -9
View File
@@ -25,7 +25,7 @@ Pod fields and Container fields.
There are two ways to expose Pod and Container fields to a running Container: There are two ways to expose Pod and Container fields to a running Container:
* Environment variables * Environment variables
* [DownwardAPIVolumeFiles](/docs/resources-reference/{{page.version}}/#downwardapivolumefile-v1-core) * [DownwardAPIVolumeFiles](/docs/api-reference/{{page.version}}/#downwardapivolumefile-v1-core)
Together, these two ways of exposing Pod and Container fields are called the Together, these two ways of exposing Pod and Container fields are called the
*Downward API*. *Downward API*.
@@ -40,7 +40,7 @@ configuration file for the Pod:
In the configuration file, you can see five environment variables. The `env` In the configuration file, you can see five environment variables. The `env`
field is an array of field is an array of
[EnvVars](/docs/resources-reference/{{page.version}}/#envvar-v1-core). [EnvVars](/docs/api-reference/{{page.version}}/#envvar-v1-core).
The first element in the array specifies that the `MY_NODE_NAME` environment The first element in the array specifies that the `MY_NODE_NAME` environment
variable gets its value from the Pod's `spec.nodeName` field. Similarly, the variable gets its value from the Pod's `spec.nodeName` field. Similarly, the
other environment variables get their names from Pod fields. other environment variables get their names from Pod fields.
@@ -118,7 +118,7 @@ container:
In the configuration file, you can see four environment variables. The `env` In the configuration file, you can see four environment variables. The `env`
field is an array of field is an array of
[EnvVars](/docs/resources-reference/{{page.version}}/#envvar-v1-core). [EnvVars](/docs/api-reference/{{page.version}}/#envvar-v1-core).
The first element in the array specifies that the `MY_CPU_REQUEST` environment The first element in the array specifies that the `MY_CPU_REQUEST` environment
variable gets its value from the `requests.cpu` field of a Container named variable gets its value from the `requests.cpu` field of a Container named
`test-container`. Similarly, the other environment variables get their values `test-container`. Similarly, the other environment variables get their values
@@ -156,12 +156,12 @@ The output shows the values of selected environment variables:
{% capture whatsnext %} {% capture whatsnext %}
* [Defining Environment Variables for a Container](/docs/tasks/inject-data-application/define-environment-variable-container/) * [Defining Environment Variables for a Container](/docs/tasks/inject-data-application/define-environment-variable-container/)
* [PodSpec](/docs/resources-reference/{{page.version}}/#podspec-v1-core) * [PodSpec](/docs/api-reference/{{page.version}}/#podspec-v1-core)
* [Container](/docs/resources-reference/{{page.version}}/#container-v1-core) * [Container](/docs/api-reference/{{page.version}}/#container-v1-core)
* [EnvVar](/docs/resources-reference/{{page.version}}/#envvar-v1-core) * [EnvVar](/docs/api-reference/{{page.version}}/#envvar-v1-core)
* [EnvVarSource](/docs/resources-reference/{{page.version}}/#envvarsource-v1-core) * [EnvVarSource](/docs/api-reference/{{page.version}}/#envvarsource-v1-core)
* [ObjectFieldSelector](/docs/resources-reference/{{page.version}}/#objectfieldselector-v1-core) * [ObjectFieldSelector](/docs/api-reference/{{page.version}}/#objectfieldselector-v1-core)
* [ResourceFieldSelector](/docs/resources-reference/{{page.version}}/#resourcefieldselector-v1-core) * [ResourceFieldSelector](/docs/api-reference/{{page.version}}/#resourcefieldselector-v1-core)
{% endcapture %} {% endcapture %}