Fix relative links issue in English content (#13307)

* `http://kubernetes.io/docs/` -> `/docs/` in content/en folder * `https://kubernetes.io/docs/` -> `/docs/` in content/en folder
2019-03-20 19:05:05 -04:00
parent 89b2eb7f64
commit 5a5f77db64
166 changed files with 522 additions and 570 deletions
@@ -16,5 +16,4 @@ tags:

 <!--more--> 

-When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](https://kubernetes.io/docs/tasks/access-kubernetes-api/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
-
+When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
@@ -2,7 +2,7 @@
 title: Cloud Controller Manager
 id: cloud-controller-manager
 date: 2018-04-12
-full_link: https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/
+full_link: /docs/tasks/administer-cluster/running-cloud-controller/
 short_description: >
  Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud.

@@ -17,4 +17,3 @@ tags:
 <!--more--> 

 Kubernetes v1.6 contains a new binary called cloud-controller-manager. cloud-controller-manager is a daemon that embeds cloud-specific control loops. These cloud-specific control loops were originally in the kube-controller-manager. Since cloud providers develop and release at a different pace compared to the Kubernetes project, abstracting the provider-specific code to the cloud-controller-manager binary allows cloud vendors to evolve independently from the core Kubernetes code.
-
@@ -2,7 +2,7 @@
 title: Container network interface (CNI)
 id: cni
 date: 2018-05-25
-full_link: https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
+full_link: /docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
 short_description: >
    Container network interface (CNI) plugins are a type of Network plugin that adheres to the appc/CNI specification.

@@ -14,5 +14,5 @@ tags:
 Container network interface (CNI) plugins are a type of Network plugin that adheres to the appc/CNI specification.
 <!--more--> 

-* For information on Kubernetes and CNI refer to [this](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
-* For information on Kubernetes and CNI, see ["Network plugins"](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
+* For information on Kubernetes and CNI refer to [this](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
+* For information on Kubernetes and CNI, see ["Network plugins"](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
@@ -14,5 +14,4 @@ tags:

 <!--more--> 

-Allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="container" >}}, so that your applications are easily portable. When storing confidential data use a [Secret](https://kubernetes.io/docs/concepts/configuration/secret/).
-
+Allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="container" >}}, so that your applications are easily portable. When storing confidential data use a [Secret](/docs/concepts/configuration/secret/).
@@ -2,7 +2,7 @@
 title: Container Storage Interface (CSI)
 id: csi
 date: 2018-06-25
-full_link: https://kubernetes.io/docs/concepts/storage/volumes/#csi
+full_link: /docs/concepts/storage/volumes/#csi
 short_description: >
    The Container Storage Interface (CSI) defines a standard interface to expose storage systems to containers.

@@ -17,5 +17,5 @@ tags:

 CSI allows vendors to create custom storage plugins for Kubernetes without adding them to the Kubernetes repository (out-of-tree plugins). To use a CSI driver from a storage provider, you must first [deploy it to your cluster](https://kubernetes-csi.github.io/docs/deploying.html). You will then be able to create a {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} that uses that CSI driver.

-* [CSI in the Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/volumes/#csi)
+* [CSI in the Kubernetes documentation](/docs/concepts/storage/volumes/#csi)
 * [List of available CSI drivers](https://kubernetes-csi.github.io/docs/drivers.html)
@@ -2,7 +2,7 @@
 title: Device Plugin
 id: device-plugin
 date: 2019-02-02
-full_link: https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
+full_link: /docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
 short_description: >
  Device Plugins are containers running in Kubernetes that provide access to a vendor specific resource.
 aka:
@@ -14,4 +14,4 @@ tags:

 <!--more-->

-[Device Plugin](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) are containers running in Kubernetes that provide access to a vendor specific resource. Device Plugins advertise these resources to kubelet and can be deployed manually or as a DeamonSet, rather than writing custom Kubernetes code.
+[Device Plugin](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) are containers running in Kubernetes that provide access to a vendor specific resource. Device Plugins advertise these resources to kubelet and can be deployed manually or as a DeamonSet, rather than writing custom Kubernetes code.
@@ -2,7 +2,7 @@
 title: Extensions
 id: Extensions
 date: 2019-02-01
-full_link: https://kubernetes.io/docs/concepts/extend-kubernetes/extend-cluster/#extensions
+full_link: /docs/concepts/extend-kubernetes/extend-cluster/#extensions
 short_description: >
  Extensions are software components that extend and deeply integrate with Kubernetes to support new types of hardware.

@@ -15,4 +15,4 @@ tags:

 <!--more-->

-Most cluster administrators will use a hosted or distribution instance of Kubernetes. As a result, most Kubernetes users will need to install [extensions](https://kubernetes.io/docs/concepts/extend-kubernetes/extend-cluster/#extensions) and fewer will need to author new ones.
+Most cluster administrators will use a hosted or distribution instance of Kubernetes. As a result, most Kubernetes users will need to install [extensions](/docs/concepts/extend-kubernetes/extend-cluster/#extensions) and fewer will need to author new ones.
@@ -2,7 +2,7 @@
 title: Flexvolume
 id: flexvolume
 date: 2018-06-25
-full_link: https://kubernetes.io/docs/concepts/storage/volumes/#flexvolume
+full_link: /docs/concepts/storage/volumes/#flexvolume
 short_description: >
    Flexvolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with Flexvolumes.

@@ -17,6 +17,6 @@ tags:

 Flexvolumes enable users to write their own drivers and add support for their volumes in Kubernetes. FlexVolume driver binaries and dependencies must be installed on host machines. This requires root access. The Storage SIG suggests implementing a {{< glossary_tooltip text="CSI" term_id="csi" >}} driver if possible since it addresses the limitations with Flexvolumes.

-* [Flexvolume in the Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/volumes/#flexvolume)
+* [Flexvolume in the Kubernetes documentation](/docs/concepts/storage/volumes/#flexvolume)
 * [More information on Flexvolumes](https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md)
 * [Volume Plugin FAQ for Storage Vendors](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md)
@@ -2,7 +2,7 @@
 title: HostAliases
 id: HostAliases
 date: 2019-01-31
-full_link: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#hostalias-v1-core
+full_link: /docs/reference/generated/kubernetes-api/v1.13/#hostalias-v1-core
 short_description: >
  A HostAliases is a mapping between the IP address and hostname to be injected into a Pod's hosts file.

@@ -14,4 +14,4 @@ tags:

 <!--more-->

-[HostAliases](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#hostalias-v1-corev) is an optional list of hostnames and IP addresses that will be injected into the Pod's hosts file if specified. This is only valid for non-hostNetwork Pods.
+[HostAliases](/docs/reference/generated/kubernetes-api/v1.13/#hostalias-v1-corev) is an optional list of hostnames and IP addresses that will be injected into the Pod's hosts file if specified. This is only valid for non-hostNetwork Pods.
@@ -15,5 +15,4 @@ tags:
 - operation
 ---

- A [Pod Disruption Budget](https://kubernetes.io/docs/concepts/workloads/pods/disruptions/) allows an application owner to create an object for a replicated application, that ensures a certain number or percentage of Pods with an assigned label will not be voluntarily evicted at any point in time. PDBs cannot prevent an involuntary disruption, but will count against the budget.
-  
+ A [Pod Disruption Budget](/docs/concepts/workloads/pods/disruptions/) allows an application owner to create an object for a replicated application, that ensures a certain number or percentage of Pods with an assigned label will not be voluntarily evicted at any point in time. PDBs cannot prevent an involuntary disruption, but will count against the budget.
@@ -16,4 +16,4 @@ short_description: >

 <!--more--> 

-The [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/) is a high level summary of where a Pod is in its lifecyle.  A Pod’s `status` field is a [PodStatus](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#podstatus-v1-core) object, which has a `phase` field that displays one of the following phases: Running, Pending, Succeeded, Failed, Unknown, Completed, or CrashLoopBackOff.
+The [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/) is a high level summary of where a Pod is in its lifecyle.  A Pod’s `status` field is a [PodStatus](/docs/reference/generated/kubernetes-api/v1.13/#podstatus-v1-core) object, which has a `phase` field that displays one of the following phases: Running, Pending, Succeeded, Failed, Unknown, Completed, or CrashLoopBackOff.
@@ -2,7 +2,7 @@
 title: Pod Priority
 id: pod-priority
 date: 2019-01-31
-full_link: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#pod-priority
+full_link: /docs/concepts/configuration/pod-priority-preemption/#pod-priority
 short_description: >
  Pod Priority indicates the importance of a Pod relative to other Pods.

@@ -14,4 +14,4 @@ tags:

 <!--more-->

-[Pod Priority](https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#pod-priority) gives the ability to set scheduling priority of a Pod to be higher and lower than other Pods — an important feature for production clusters workload.
+[Pod Priority](/docs/concepts/configuration/pod-priority-preemption/#pod-priority) gives the ability to set scheduling priority of a Pod to be higher and lower than other Pods — an important feature for production clusters workload.
@@ -2,7 +2,7 @@
 title: Preemption
 id: preemption
 date: 2019-01-31
-full_link: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#preemption
+full_link: /docs/concepts/configuration/pod-priority-preemption/#preemption
 short_description: >
  Preemption logic in Kubernetes helps a pending Pod to find a suitable Node by evicting low priority Pods existing on that Node.

@@ -14,4 +14,4 @@ tags:

 <!--more-->

-If a Pod cannot be scheduled, the scheduler tries to [preempt](https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#preemption) lower priority Pods to make scheduling of the pending Pod possible.
+If a Pod cannot be scheduled, the scheduler tries to [preempt](/docs/concepts/configuration/pod-priority-preemption/#preemption) lower priority Pods to make scheduling of the pending Pod possible.
@@ -2,7 +2,7 @@
 title: ReplicaSet
 id: replica-set
 date: 2018-04-12
-full_link: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
+full_link: /docs/concepts/workloads/controllers/replicaset/
 short_description: >
  ReplicaSet is the next-generation Replication Controller.

@@ -17,4 +17,3 @@ tags:
 <!--more--> 

 ReplicaSet, like ReplicationController, ensures that a specified number of pods replicas are running at one time. ReplicaSet supports the new set-based selector requirements as described in the labels user guide, whereas a Replication Controller only supports equality-based selector requirements.
-
@@ -15,5 +15,4 @@ tags:

 <!--more--> 

-Allows for more control over how sensitive information is used and reduces the risk of accidental exposure, including [encryption](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted) at rest.  A {{< glossary_tooltip text="Pod" term_id="pod" >}} references the secret as a file in a volume mount or by the kubelet pulling images for a pod. Secrets are great for confidential data and [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) for non-confidential data.
-
+Allows for more control over how sensitive information is used and reduces the risk of accidental exposure, including [encryption](/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted) at rest.  A {{< glossary_tooltip text="Pod" term_id="pod" >}} references the secret as a file in a volume mount or by the kubelet pulling images for a pod. Secrets are great for confidential data and [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/) for non-confidential data.