From fda7ed44df955b8bcb6bf9887af409abffab2615 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Wed, 4 Oct 2017 16:07:41 -0700 Subject: [PATCH] Update links to avoid redirects. (#5765) --- docs/concepts/architecture/nodes.md | 10 +++++----- .../manage-compute-resources-container.md | 4 ++-- .../fedora/flannel_multi_node_cluster.md | 6 +++--- docs/getting-started-guides/libvirt-coreos.md | 2 +- docs/home/contribute/create-pull-request.md | 4 ++-- docs/home/contribute/review-issues.md | 4 ++-- docs/home/contribute/write-new-topic.md | 2 +- .../configure-pod-container/configure-pod-configmap.md | 8 ++++---- .../debug-application-introspection.md | 8 ++++---- 9 files changed, 24 insertions(+), 24 deletions(-) diff --git a/docs/concepts/architecture/nodes.md b/docs/concepts/architecture/nodes.md index c88945eced..478e4b463a 100644 --- a/docs/concepts/architecture/nodes.md +++ b/docs/concepts/architecture/nodes.md @@ -12,7 +12,7 @@ title: Nodes A `node` is a worker machine in Kubernetes, previously known as a `minion`. A node may be a VM or physical machine, depending on the cluster. Each node has -the services necessary to run [pods](/docs/user-guide/pods) and is managed by the master +the services necessary to run [pods](/docs/concepts/workloads/pods/pod/) and is managed by the master components. The services on a node include Docker, kubelet and kube-proxy. See [The Kubernetes Node](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md#the-kubernetes-node) section in the architecture design doc for more details. @@ -64,7 +64,7 @@ The node condition is represented as a JSON object. For example, the following r ] ``` -If the Status of the Ready condition is "Unknown" or "False" for longer than the `pod-eviction-timeout`, an argument is passed to the [kube-controller-manager](/docs/admin/kube-controller-manager) and all of the Pods on the node are scheduled for deletion by the Node Controller. The default eviction timeout duration is **five minutes**. In some cases when the node is unreachable, the apiserver is unable to communicate with the kubelet on it. The decision to delete the pods cannot be communicated to the kubelet until it re-establishes communication with the apiserver. In the meantime, the pods which are scheduled for deletion may continue to run on the partitioned node. +If the Status of the Ready condition is "Unknown" or "False" for longer than the `pod-eviction-timeout`, an argument is passed to the [kube-controller-manager](/docs/admin/kube-controller-manager/) and all of the Pods on the node are scheduled for deletion by the Node Controller. The default eviction timeout duration is **five minutes**. In some cases when the node is unreachable, the apiserver is unable to communicate with the kubelet on it. The decision to delete the pods cannot be communicated to the kubelet until it re-establishes communication with the apiserver. In the meantime, the pods which are scheduled for deletion may continue to run on the partitioned node. In versions of Kubernetes prior to 1.5, the node controller would [force delete](/docs/concepts/workloads/pods/pod/#force-deletion-of-pods) these unreachable pods from the apiserver. However, in 1.5 and higher, the node controller does not force delete pods until it is @@ -74,7 +74,7 @@ permanently left a cluster, the cluster administrator may need to delete the nod Kubernetes causes all the Pod objects running on it to be deleted from the apiserver, freeing up their names. Version 1.8 introduces an alpha feature that automatically creates -[taints](/docs/concepts/configuration/taint-and-toleration) that represent conditions. +[taints](/docs/concepts/configuration/taint-and-toleration/) that represent conditions. To enable this behavior, pass an additional feature gate flag `--feature-gates=...,TaintNodesByCondition=true` to the API server, controller manager, and scheduler. When `TaintNodesByCondition` is enabled, the scheduler ignores conditions when considering a Node; instead @@ -101,7 +101,7 @@ The information is gathered by Kubelet from the node. ## Management -Unlike [pods](/docs/user-guide/pods) and [services](/docs/user-guide/services), +Unlike [pods](/docs/concepts/workloads/pods/pod/) and [services](/docs/concepts/workloads/pods/pod/), a node is not inherently created by Kubernetes: it is created externally by cloud providers like Google Compute Engine, or exists in your pool of physical or virtual machines. What this means is that when Kubernetes creates a node, it is really @@ -192,7 +192,7 @@ Starting in Kubernetes 1.6, the NodeController is also responsible for evicting pods that are running on nodes with `NoExecute` taints, when the pods do not tolerate the taints. Additionally, as an alpha feature that is disabled by default, the NodeController is responsible for adding taints corresponding to node problems like -node unreachable or not ready. See [this documentation](/docs/concepts/configuration/taint-and-toleration) +node unreachable or not ready. See [this documentation](/docs/concepts/configuration/taint-and-toleration/) for details about `NoExecute` taints and the alpha feature. Starting in version 1.8, the node controller can be made responsible for creating taints that represent diff --git a/docs/concepts/configuration/manage-compute-resources-container.md b/docs/concepts/configuration/manage-compute-resources-container.md index 475d859044..f9146b58d6 100644 --- a/docs/concepts/configuration/manage-compute-resources-container.md +++ b/docs/concepts/configuration/manage-compute-resources-container.md @@ -4,7 +4,7 @@ title: Managing Compute Resources for Containers {% capture overview %} -When you specify a [Pod](/docs/user-guide/pods), you can optionally specify how +When you specify a [Pod](/docs/concepts/workloads/pods/pod/), you can optionally specify how much CPU and memory (RAM) each Container needs. When Containers have resource requests specified, the scheduler can make better decisions about which nodes to place Pods on. And when Containers have their limits specified, contention for @@ -27,7 +27,7 @@ CPU and memory are collectively referred to as *compute resources*, or just resources are measurable quantities that can be requested, allocated, and consumed. They are distinct from [API resources](/docs/concepts/overview/kubernetes-api/). API resources, such as Pods and -[Services](/docs/user-guide/services) are objects that can be read and modified +[Services](/docs/concepts/services-networking/service/) are objects that can be read and modified through the Kubernetes API server. ## Resource requests and limits of Pod and Container diff --git a/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md b/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md index 51d3aa0db3..dbd3de0080 100644 --- a/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md +++ b/docs/getting-started-guides/fedora/flannel_multi_node_cluster.md @@ -188,9 +188,9 @@ Now Kubernetes multi-node cluster is set up with overlay networking set up by fl IaaS Provider | Config. Mgmt | OS | Networking | Docs | Conforms | Support Level -------------------- | ------------ | ------ | ---------- | --------------------------------------------- | ---------| ---------------------------- -Bare-metal | custom | Fedora | flannel | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster) | | Community ([@aveshagarwal](https://github.com/aveshagarwal)) -libvirt | custom | Fedora | flannel | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster) | | Community ([@aveshagarwal](https://github.com/aveshagarwal)) -KVM | custom | Fedora | flannel | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster) | | Community ([@aveshagarwal](https://github.com/aveshagarwal)) +Bare-metal | custom | Fedora | flannel | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/) | | Community ([@aveshagarwal](https://github.com/aveshagarwal)) +libvirt | custom | Fedora | flannel | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/) | | Community ([@aveshagarwal](https://github.com/aveshagarwal)) +KVM | custom | Fedora | flannel | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/) | | Community ([@aveshagarwal](https://github.com/aveshagarwal)) diff --git a/docs/getting-started-guides/libvirt-coreos.md b/docs/getting-started-guides/libvirt-coreos.md index 4c067f8d65..16fe70d66c 100644 --- a/docs/getting-started-guides/libvirt-coreos.md +++ b/docs/getting-started-guides/libvirt-coreos.md @@ -332,7 +332,7 @@ Ensure libvirtd has been restarted since ebtables was installed. IaaS Provider | Config. Mgmt | OS | Networking | Docs | Conforms | Support Level -------------------- | ------------ | ------ | ---------- | --------------------------------------------- | ---------| ---------------------------- -libvirt/KVM | CoreOS | CoreOS | libvirt/KVM | [docs](/docs/getting-started-guides/libvirt-coreos) | | Community ([@lhuard1A](https://github.com/lhuard1A)) +libvirt/KVM | CoreOS | CoreOS | libvirt/KVM | [docs](/docs/getting-started-guides/libvirt-coreos/) | | Community ([@lhuard1A](https://github.com/lhuard1A)) For support level information on all solutions, see the [Table of solutions](/docs/getting-started-guides/#table-of-solutions) chart. diff --git a/docs/home/contribute/create-pull-request.md b/docs/home/contribute/create-pull-request.md index bc408e9e54..733e18fe75 100644 --- a/docs/home/contribute/create-pull-request.md +++ b/docs/home/contribute/create-pull-request.md @@ -90,9 +90,9 @@ next upcoming release. It's automatically updated as new PRs get merged. {% endcapture %} {% capture whatsnext %} -* Learn about [writing a new topic](/docs/home/contribute/write-new-topic). +* Learn about [writing a new topic](/docs/home/contribute/write-new-topic/). * Learn about [using page templates](/docs/home/contribute/page-templates/). -* Learn about [staging your changes](/docs/home/contribute/stage-documentation-changes). +* Learn about [staging your changes](/docs/home/contribute/stage-documentation-changes/). {% endcapture %} {% include templates/task.md %} diff --git a/docs/home/contribute/review-issues.md b/docs/home/contribute/review-issues.md index 815edff9c9..047cc6936f 100644 --- a/docs/home/contribute/review-issues.md +++ b/docs/home/contribute/review-issues.md @@ -65,9 +65,9 @@ Depending on where the dead link is reported, different actions are required to {% capture whatsnext %} -* Learn about [writing a new topic](/docs/home/contribute/write-new-topic). +* Learn about [writing a new topic](/docs/home/contribute/write-new-topic/). * Learn about [using page templates](/docs/home/contribute/page-templates/). -* Learn about [staging your changes](/docs/home/contribute/stage-documentation-changes). +* Learn about [staging your changes](/docs/home/contribute/stage-documentation-changes/). {% endcapture %} {% include templates/concept.md %} diff --git a/docs/home/contribute/write-new-topic.md b/docs/home/contribute/write-new-topic.md index 6dde02a322..440efec467 100644 --- a/docs/home/contribute/write-new-topic.md +++ b/docs/home/contribute/write-new-topic.md @@ -136,7 +136,7 @@ image format is SVG. {% capture whatsnext %} * Learn about [using page templates](/docs/home/contribute/page-templates/). -* Learn about [staging your changes](/docs/home/contribute/stage-documentation-changes). +* Learn about [staging your changes](/docs/home/contribute/stage-documentation-changes/). * Learn about [creating a pull request](/docs/home/contribute/create-pull-request/). {% endcapture %} diff --git a/docs/tasks/configure-pod-container/configure-pod-configmap.md b/docs/tasks/configure-pod-container/configure-pod-configmap.md index 7286accd9a..91fd9670f1 100644 --- a/docs/tasks/configure-pod-container/configure-pod-configmap.md +++ b/docs/tasks/configure-pod-container/configure-pod-configmap.md @@ -24,7 +24,7 @@ This page provides a series of usage examples demonstrating how to configure Pod kubectl create configmap special-config --from-literal=special.how=very ``` -1. Assign the `special.how` value defined in the ConfigMap to the `SPECIAL_LEVEL_KEY` environment variable in the Pod specification. +1. Assign the `special.how` value defined in the ConfigMap to the `SPECIAL_LEVEL_KEY` environment variable in the Pod specification. ```shell kubectl edit pod dapi-test-pod @@ -78,7 +78,7 @@ This page provides a series of usage examples demonstrating how to configure Pod log_level: INFO ``` -1. Define the environment variables in the Pod specification. +1. Define the environment variables in the Pod specification. ```yaml apiVersion: v1 @@ -272,7 +272,7 @@ very ### Project keys to specific paths and file permissions You can project keys to specific paths and specific permissions on a per-file -basis. The [Secrets](/docs/concepts/configuration/secret#using-secrets-as-files-from-a-pod) user guide explains the syntax. +basis. The [Secrets](/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod) user guide explains the syntax. ### Mounted ConfigMaps are updated automatically @@ -296,7 +296,7 @@ When a ConfigMap already being consumed in a volume is updated, projected keys a 0s 0s 1 dapi-test-pod Pod Warning InvalidEnvironmentVariableNames {kubelet, 127.0.0.1} Keys [1badkey, 2alsobad] from the EnvFrom configMap default/myconfig were skipped since they are considered invalid environment variable names. ``` -1. ConfigMaps reside in a specific [namespace](/docs/user-guide/namespaces/). A ConfigMap can only be referenced by pods residing in the same namespace. +1. ConfigMaps reside in a specific [namespace](/docs/concepts/overview/working-with-objects/namespaces/). A ConfigMap can only be referenced by pods residing in the same namespace. 1. Kubelet doesn't support the use of ConfigMaps for pods not found on the API server. This includes every pod created using kubectl or indirectly via a replication controller. diff --git a/docs/tasks/debug-application-cluster/debug-application-introspection.md b/docs/tasks/debug-application-cluster/debug-application-introspection.md index 292e86a363..a149efba6f 100644 --- a/docs/tasks/debug-application-cluster/debug-application-introspection.md +++ b/docs/tasks/debug-application-cluster/debug-application-introspection.md @@ -376,10 +376,10 @@ status: Learn about additional debugging tools, including: -* [Logging](/docs/user-guide/logging/overview) -* [Monitoring](/docs/user-guide/monitoring) -* [Getting into containers via `exec`](/docs/user-guide/getting-into-containers) +* [Logging](/docs/concepts/cluster-administration/logging/) +* [Monitoring](/docs/tasks/debug-application-cluster/resource-usage-monitoring/) +* [Getting into containers via `exec`](/docs/tasks/debug-application-cluster/get-shell-running-container/) * [Connecting to containers via proxies](/docs/tasks/access-kubernetes-api/http-proxy-access-api/) -* [Connecting to containers via port forwarding](/docs/user-guide/connecting-to-applications-port-forward) +* [Connecting to containers via port forwarding](/docs/tasks/access-application-cluster/port-forward-access-application-cluster/)