en: Change the full link in the document to an inline link. (#17057)

* Change the full link in the document to an inline link.

grep -r "https \: \ / \ / kubernetes \ .io" content/en/docs
Changed to inline link except the following list.
- URLs are mentioned directly in the body
- release note
- url to blog
- url to community
- Url to be redirected

* Apply suggestions from code review

Co-Authored-By: June Yi <june.yi@samsung.com>

content/en/docs/concepts/configuration/pod-overhead.md

@@ -27,9 +27,9 @@ on top of the container requests & limits.
 ## Pod Overhead
 
 In Kubernetes, the pod's overhead is set at
-[admission](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#what-are-admission-webhooks)
+[admission](/docs/reference/access-authn-authz/extensible-admission-controllers/#what-are-admission-webhooks)
 time according to the overhead associated with the pod's
-[RuntimeClass](https://kubernetes.io/docs/concepts/containers/runtime-class/).
+[RuntimeClass](/docs/concepts/containers/runtime-class/).
 
 When Pod Overhead is enabled, the overhead is considered in addition to the sum of container
 resource requests when scheduling a pod. Similarly, Kubelet will include the pod overhead when sizing

content/en/docs/concepts/configuration/pod-priority-preemption.md

@@ -156,7 +156,7 @@ description: "This priority class should be used for XYZ service pods only."
 
 1.15 adds the `PreemptionPolicy` field as an alpha feature.
 It is disabled by default in 1.15,
-and requires the `NonPreemptingPriority`[feature gate](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/
+and requires the `NonPreemptingPriority`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/
 ) to be enabled.
 
 Pods with `PreemptionPolicy: Never` will be placed in the scheduling queue

content/en/docs/concepts/scheduling/kube-scheduler.md

@@ -174,7 +174,7 @@ kube-scheduler has a default set of scheduling policies.
   that the Service becomes more resilient to a single Node failure.
 
 - `CalculateAntiAffinityPriorityMap`: This policy helps implement
-  [pod anti-affinity](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
+  [pod anti-affinity](/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
 
 - `EqualPriorityMap`: Gives an equal weight of one to all nodes.
 

content/en/docs/concepts/services-networking/dual-stack.md

@@ -45,7 +45,7 @@ The following prerequisites are needed in order to utilize IPv4/IPv6 dual-stack
 
 ## Enable IPv4/IPv6 dual-stack
 
-To enable IPv4/IPv6 dual-stack, enable the `IPv6DualStack` [feature gate](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/) for the relevant components of your cluster, and set dual-stack cluster network assignments:
+To enable IPv4/IPv6 dual-stack, enable the `IPv6DualStack` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the relevant components of your cluster, and set dual-stack cluster network assignments:
 
    * kube-controller-manager:
       * `--feature-gates="IPv6DualStack=true"`

content/en/docs/concepts/storage/volumes.md

@@ -214,7 +214,7 @@ See the [CephFS example](https://github.com/kubernetes/examples/tree/{{< param "
 
 {{< note >}}
 Prerequisite: Kubernetes with OpenStack Cloud Provider configured. For cloudprovider
-configuration please refer [cloud provider openstack](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#openstack).
+configuration please refer [cloud provider openstack](/docs/concepts/cluster-administration/cloud-providers/#openstack).
 {{< /note >}}
 
 `cinder` is used to mount OpenStack Cinder Volume into your Pod.

content/en/docs/concepts/workloads/pods/pod-overview.md

@@ -21,7 +21,7 @@ A *Pod* is the basic execution unit of a Kubernetes application--the smallest an
 
 A Pod encapsulates an application's container (or, in some cases, multiple containers), storage resources, a unique network IP, and options that govern how the container(s) should run. A Pod represents a unit of deployment: *a single instance of an application in Kubernetes*, which might consist of either a single {{< glossary_tooltip text="container" term_id="container" >}} or a small number of containers that are tightly coupled and that share resources.
 
-[Docker](https://www.docker.com) is the most common container runtime used in a Kubernetes Pod, but Pods support other [container runtimes](https://kubernetes.io/docs/setup/production-environment/container-runtimes/) as well.
+[Docker](https://www.docker.com) is the most common container runtime used in a Kubernetes Pod, but Pods support other [container runtimes](/docs/setup/production-environment/container-runtimes/) as well.
 
 
 Pods in a Kubernetes cluster can be used in two main ways: