From d2de692a325ddea02e5448de3cced9a0be68d6f5 Mon Sep 17 00:00:00 2001 From: Arthur Miranda Date: Tue, 2 May 2017 18:12:48 -0300 Subject: [PATCH] Fixes broken links --- docs/concepts/cluster-administration/cluster-management.md | 2 +- docs/concepts/cluster-administration/manage-deployment.md | 2 +- docs/concepts/cluster-administration/out-of-resource.md | 2 +- .../cluster-administration/resource-usage-monitoring.md | 2 +- docs/concepts/containers/container-environment-variables.md | 2 +- docs/concepts/containers/container-lifecycle-hooks.md | 2 +- docs/concepts/storage/persistent-volumes.md | 2 +- docs/concepts/workloads/pods/pod.md | 2 +- docs/getting-started-guides/mesos/index.md | 2 +- docs/reference/federation/index.md | 6 +++--- docs/setup/pick-right-solution.md | 2 +- 11 files changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/concepts/cluster-administration/cluster-management.md b/docs/concepts/cluster-administration/cluster-management.md index 54ccffac30..813f2976e7 100644 --- a/docs/concepts/cluster-administration/cluster-management.md +++ b/docs/concepts/cluster-administration/cluster-management.md @@ -201,4 +201,4 @@ You can use `kubectl convert` command to convert config files between different kubectl convert -f pod.yaml --output-version v1 ``` -For more options, please refer to the usage of [kubectl convert](/docs/user-guide/kubectl/kubectl_convert/) command. +For more options, please refer to the usage of [kubectl convert](/docs/user-guide/kubectl/v1.6/#convert) command. diff --git a/docs/concepts/cluster-administration/manage-deployment.md b/docs/concepts/cluster-administration/manage-deployment.md index 4e8f031a3f..94ff007595 100644 --- a/docs/concepts/cluster-administration/manage-deployment.md +++ b/docs/concepts/cluster-administration/manage-deployment.md @@ -304,7 +304,7 @@ deployment "my-nginx" autoscaled Now your nginx replicas will be scaled up and down as needed, automatically. -For more information, please see [kubectl scale](/docs/user-guide/kubectl/v1.6/#scale), [kubectl autoscale](/docs/user-guide/kubectl/v1.6/#autoscale) and [horizontal pod autoscaler](/docs/user-guide/horizontal-pod-autoscaler/) document. +For more information, please see [kubectl scale](/docs/user-guide/kubectl/v1.6/#scale), [kubectl autoscale](/docs/user-guide/kubectl/v1.6/#autoscale) and [horizontal pod autoscaler](/docs/tasks/run-application/horizontal-pod-autoscale/) document. ## In-place updates of resources diff --git a/docs/concepts/cluster-administration/out-of-resource.md b/docs/concepts/cluster-administration/out-of-resource.md index fd7178d841..1144f371fb 100644 --- a/docs/concepts/cluster-administration/out-of-resource.md +++ b/docs/concepts/cluster-administration/out-of-resource.md @@ -49,7 +49,7 @@ associated with each signal. The value for `memory.available` is derived from the cgroupfs instead of tools like `free -m`. This is important because `free -m` does not work in a container, and if users use the [node -allocatable](/docs/admin/node-allocatable.md) feature, out of resource decisions +allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable) feature, out of resource decisions are made local to the end user pod part of the cgroup hierarchy as well as the root node. This [script](/docs/concepts/cluster-administration/out-of-resource/memory-available.sh) diff --git a/docs/concepts/cluster-administration/resource-usage-monitoring.md b/docs/concepts/cluster-administration/resource-usage-monitoring.md index 86061e852b..c28cb35b4a 100644 --- a/docs/concepts/cluster-administration/resource-usage-monitoring.md +++ b/docs/concepts/cluster-administration/resource-usage-monitoring.md @@ -11,7 +11,7 @@ Understanding how an application behaves when deployed is crucial to scaling the ## Overview -Heapster is a cluster-wide aggregator of monitoring and event data. It currently supports Kubernetes natively and works on all Kubernetes setups. Heapster runs as a pod in the cluster, similar to how any Kubernetes application would run. The Heapster pod discovers all nodes in the cluster and queries usage information from the nodes' [Kubelet](https://releases.k8s.io/{{page.githubbranch}}/DESIGN.md#kubelet)s, the on-machine Kubernetes agent. The Kubelet itself fetches the data from [cAdvisor](https://github.com/google/cadvisor). Heapster groups the information by pod along with the relevant labels. This data is then pushed to a configurable backend for storage and visualization. Currently supported backends include [InfluxDB](http://influxdb.com/) (with [Grafana](http://grafana.org/) for visualization), [Google Cloud Monitoring](https://cloud.google.com/monitoring/) and many others described in more details [here](https://github.com/kubernetes/heapster/blob/master/docs/sink-configuration.md). The overall architecture of the service can be seen below: +Heapster is a cluster-wide aggregator of monitoring and event data. It currently supports Kubernetes natively and works on all Kubernetes setups. Heapster runs as a pod in the cluster, similar to how any Kubernetes application would run. The Heapster pod discovers all nodes in the cluster and queries usage information from the nodes' [Kubelet](/docs/admin/kubelet/)s, the on-machine Kubernetes agent. The Kubelet itself fetches the data from [cAdvisor](https://github.com/google/cadvisor). Heapster groups the information by pod along with the relevant labels. This data is then pushed to a configurable backend for storage and visualization. Currently supported backends include [InfluxDB](http://influxdb.com/) (with [Grafana](http://grafana.org/) for visualization), [Google Cloud Monitoring](https://cloud.google.com/monitoring/) and many others described in more details [here](https://github.com/kubernetes/heapster/blob/master/docs/sink-configuration.md). The overall architecture of the service can be seen below: ![overall monitoring architecture](/images/docs/monitoring-architecture.png) diff --git a/docs/concepts/containers/container-environment-variables.md b/docs/concepts/containers/container-environment-variables.md index 16276c90b4..364789c338 100644 --- a/docs/concepts/containers/container-environment-variables.md +++ b/docs/concepts/containers/container-environment-variables.md @@ -56,7 +56,7 @@ if [DNS addon](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/) {% capture whatsnext %} -* Learn more about [Container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks.md). +* Learn more about [Container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/). * Get hands-on experience [attaching handlers to Container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/). diff --git a/docs/concepts/containers/container-lifecycle-hooks.md b/docs/concepts/containers/container-lifecycle-hooks.md index 206e86fb40..5b72cabba1 100644 --- a/docs/concepts/containers/container-lifecycle-hooks.md +++ b/docs/concepts/containers/container-lifecycle-hooks.md @@ -118,7 +118,7 @@ Events: {% capture whatsnext %} -* Learn more about the [Container environment](/docs/concepts/containers/container-environment-variables.md). +* Learn more about the [Container environment](/docs/concepts/containers/container-environment-variables/). * Get hands-on experience [attaching handlers to Container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/). diff --git a/docs/concepts/storage/persistent-volumes.md b/docs/concepts/storage/persistent-volumes.md index 11d27364e6..a17df8ab94 100644 --- a/docs/concepts/storage/persistent-volumes.md +++ b/docs/concepts/storage/persistent-volumes.md @@ -493,7 +493,7 @@ parameters: ``` $ kubectl create secret generic heketi-secret --type="kubernetes.io/glusterfs" --from-literal=key='opensesame' --namespace=default ``` - Example of a secret can be found in [glusterfs-provisioning-secret.yaml](https://github.com/kubernetes/kubernetes/blob/master/examples/persistent-volume-provisioning/glusterfs-provisioning-secret.yaml). + Example of a secret can be found in [glusterfs-provisioning-secret.yaml](https://github.com/kubernetes/kubernetes/blob/master/examples/persistent-volume-provisioning/glusterfs/glusterfs-secret.yaml). * `clusterid`: `630372ccdc720a92c681fb928f27b53f` is the ID of the cluster which will be used by Heketi when provisioning the volume. It can also be a list of clusterids, for ex: "8452344e2becec931ece4e33c4674e4e,42982310de6c63381718ccfa6d8cf397". This is an optional parameter. * `gidMin`, `gidMax` : The minimum and maximum value of GID range for the storage class. A unique value (GID) in this range ( gidMin-gidMax ) will be used for dynamically provisioned volumes. These are optional values. If not specified, the volume will be provisioned with a value between 2000-2147483647 which are defaults for gidMin and gidMax respectively. diff --git a/docs/concepts/workloads/pods/pod.md b/docs/concepts/workloads/pods/pod.md index d19c601b78..d399ad550d 100644 --- a/docs/concepts/workloads/pods/pod.md +++ b/docs/concepts/workloads/pods/pod.md @@ -142,7 +142,7 @@ Pods aren't intended to be treated as durable entities. They won't survive sched In general, users shouldn't need to create pods directly. They should almost always use controllers (e.g., [Deployments](/docs/concepts/workloads/controllers/deployment/)), even for singletons. Controllers provide self-healing with a cluster scope, as well as replication and rollout management. -The use of collective APIs as the primary user-facing primitive is relatively common among cluster scheduling systems, including [Borg](https://research.google.com/pubs/pub43438.html), [Marathon](https://mesosphere.github.io/marathon/docs/rest-api.html), [Aurora](http://aurora.apache.org/documentation/latest/configuration-reference/#job-schema), and [Tupperware](http://www.slideshare.net/Docker/aravindnarayanan-facebook140613153626phpapp02-37588997). +The use of collective APIs as the primary user-facing primitive is relatively common among cluster scheduling systems, including [Borg](https://research.google.com/pubs/pub43438.html), [Marathon](https://mesosphere.github.io/marathon/docs/rest-api.html), [Aurora](http://aurora.apache.org/documentation/latest/reference/configuration/#job-schema), and [Tupperware](http://www.slideshare.net/Docker/aravindnarayanan-facebook140613153626phpapp02-37588997). Pod is exposed as a primitive in order to facilitate: diff --git a/docs/getting-started-guides/mesos/index.md b/docs/getting-started-guides/mesos/index.md index b30482a9a1..f76ae95180 100644 --- a/docs/getting-started-guides/mesos/index.md +++ b/docs/getting-started-guides/mesos/index.md @@ -30,7 +30,7 @@ Further information is available in the Kubernetes on Mesos [contrib directory][ - A running [Mesos cluster on Google Compute Engine][5] - A [VPN connection][10] to the cluster - A machine in the cluster which should become the Kubernetes *master node* with: - - Go (see [here](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/devel/development.md#go-versions) for required versions) + - Go (see [here](https://github.com/kubernetes/community/blob/master/contributors/devel/development.md) for required versions) - make (i.e. build-essential) - Docker diff --git a/docs/reference/federation/index.md b/docs/reference/federation/index.md index 7aa794f470..1cadb737e7 100644 --- a/docs/reference/federation/index.md +++ b/docs/reference/federation/index.md @@ -7,9 +7,9 @@ redirect_from: Federation API server supports the following group versions: -* federation/v1beta1: [operations](/docs/reference/federation/v1beta1/operations.html), [model definitions](/docs/reference/federation/v1beta1/definitions.html) -* v1: [operations](/docs/reference/federation/v1/operations.html), [model definitions](/docs/reference/federation/v1/definitions.html) -* extensions/v1beta1: [operations](/docs/reference/federation/extensions/v1beta1/operations.html), [model definitions](/docs/reference/federation/extensions/v1beta1/definitions.html) +* federation/v1beta1: [operations](/docs/reference/federation/v1beta1/operations/), [model definitions](/docs/reference/federation/v1beta1/definitions/) +* v1: [operations](/docs/reference/federation/v1/operations/), [model definitions]/docs/reference/federation/v1/definitions/) +* extensions/v1beta1: [operations](/docs/reference/federation/extensions/v1beta1/operations/), [model definitions](/docs/reference/federation/extensions/v1beta1/definitions/) diff --git a/docs/setup/pick-right-solution.md b/docs/setup/pick-right-solution.md index 6cd8e830f0..c8d44755e4 100644 --- a/docs/setup/pick-right-solution.md +++ b/docs/setup/pick-right-solution.md @@ -172,7 +172,7 @@ AWS | CoreOS | CoreOS | flannel | [docs](/docs/gettin GCE | CoreOS | CoreOS | flannel | [docs](/docs/getting-started-guides/coreos) | Community ([@pires](https://github.com/pires)) Vagrant | CoreOS | CoreOS | flannel | [docs](/docs/getting-started-guides/coreos) | Community ([@pires](https://github.com/pires), [@AntonioMeireles](https://github.com/AntonioMeireles)) Bare-metal (Offline) | CoreOS | CoreOS | flannel | [docs](/docs/getting-started-guides/coreos/bare_metal_offline) | Community ([@jeffbean](https://github.com/jeffbean)) -CloudStack | Ansible | CoreOS | flannel | [docs](/docs/getting-started-guides/cloudstack) | Community ([@runseb](https://github.com/runseb)) +CloudStack | Ansible | CoreOS | flannel | [docs](/docs/getting-started-guides/cloudstack) | Community ([@sebgoa](https://github.com/sebgoa)) Vmware vSphere | Saltstack | Debian | OVS | [docs](/docs/getting-started-guides/vsphere) | Community ([@imkin](https://github.com/imkin)) Vmware Photon | Saltstack | Debian | OVS | [docs](/docs/getting-started-guides/photon-controller) | Community ([@alainroy](https://github.com/alainroy)) Bare-metal | custom | CentOS | flannel | [docs](/docs/getting-started-guides/centos/centos_manual_config) | Community ([@coolsvap](https://github.com/coolsvap))