From e227272f5c43f81b8ea30c42a980a2c0c88e861a Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Mon, 25 Sep 2017 16:43:35 -0700 Subject: [PATCH] Fix 404s. (#5623) --- docs/concepts/storage/persistent-volumes.md | 2 +- docs/concepts/workloads/controllers/petset.md | 2 +- .../load-balance-access-application-cluster.md | 2 +- .../service-access-application-cluster.md | 2 +- docs/tasks/administer-cluster/securing-a-cluster.md | 2 +- docs/tools/kompose/user-guide.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/concepts/storage/persistent-volumes.md b/docs/concepts/storage/persistent-volumes.md index 19a17e0491..96ebfed733 100644 --- a/docs/concepts/storage/persistent-volumes.md +++ b/docs/concepts/storage/persistent-volumes.md @@ -35,7 +35,7 @@ administrators. Kubernetes itself is unopinionated about what classes represent. This concept is sometimes called "profiles" in other storage systems. -Please see the [detailed walkthrough with working examples](/docs/concepts/storage/persistent-volumes/walkthrough/). +Please see the [detailed walkthrough with working examples](/docs/tasks/configure-pod-container/configure-persistent-volume-storage/). ## Lifecycle of a volume and claim diff --git a/docs/concepts/workloads/controllers/petset.md b/docs/concepts/workloads/controllers/petset.md index c884679821..2ec7151d1b 100644 --- a/docs/concepts/workloads/controllers/petset.md +++ b/docs/concepts/workloads/controllers/petset.md @@ -24,7 +24,7 @@ Throughout this doc you will see a few terms that are sometimes used interchange * Node: A single virtual or physical machine in a Kubernetes cluster. * Cluster: A group of nodes in a single failure domain, unless mentioned otherwise. -* Persistent Volume Claim (PVC): A request for storage, typically a [persistent volume](/docs/concepts/storage/persistent-volumes/walkthrough/). +* Persistent Volume Claim (PVC): A request for storage, typically a [persistent volume](/docs/tasks/configure-pod-container/configure-persistent-volume-storage/). * Host name: The hostname attached to the UTS namespace of the pod, i.e. the output of `hostname` in the pod. * DNS/Domain name: A *cluster local* domain name resolvable using standard methods (e.g.: [gethostbyname](http://linux.die.net/man/3/gethostbyname)). * Ordinality: the property of being "ordinal", or occupying a position in a sequence. diff --git a/docs/tasks/access-application-cluster/load-balance-access-application-cluster.md b/docs/tasks/access-application-cluster/load-balance-access-application-cluster.md index e4f59bff75..458dc2062e 100644 --- a/docs/tasks/access-application-cluster/load-balance-access-application-cluster.md +++ b/docs/tasks/access-application-cluster/load-balance-access-application-cluster.md @@ -101,7 +101,7 @@ load-balanced access to an application running in a cluster. ## Using a service configuration file As an alternative to using `kubectl expose`, you can use a -[service configuration file](/docs/concepts/services-networking/service/operations) +[service configuration file](/docs/concepts/services-networking/service/) to create a Service. diff --git a/docs/tasks/access-application-cluster/service-access-application-cluster.md b/docs/tasks/access-application-cluster/service-access-application-cluster.md index 84909650c7..212e1be9e6 100644 --- a/docs/tasks/access-application-cluster/service-access-application-cluster.md +++ b/docs/tasks/access-application-cluster/service-access-application-cluster.md @@ -117,7 +117,7 @@ provides load balancing for an application that has two running instances. ## Using a service configuration file As an alternative to using `kubectl expose`, you can use a -[service configuration file](/docs/concepts/services-networking/service/operations) +[service configuration file](/docs/concepts/services-networking/service/) to create a Service. {% endcapture %} diff --git a/docs/tasks/administer-cluster/securing-a-cluster.md b/docs/tasks/administer-cluster/securing-a-cluster.md index 6df8e0f1b3..b967a01138 100644 --- a/docs/tasks/administer-cluster/securing-a-cluster.md +++ b/docs/tasks/administer-cluster/securing-a-cluster.md @@ -82,7 +82,7 @@ resources granted to a namespace. This is most often used to limit the amount of or persistent disk a namespace can allocate, but can also control how many pods, services, or volumes exist in each namespace. -[Limit ranges](/docs/admin/limitrange) restrict the maximum or minimum size of some of the +[Limit ranges](/docs/tasks/administer-cluster/memory-default-namespace/) restrict the maximum or minimum size of some of the resources above, to prevent users from requesting unreasonably high or low values for commonly reserved resources like memory, or to provide default limits when none are specified. diff --git a/docs/tools/kompose/user-guide.md b/docs/tools/kompose/user-guide.md index efd2b1c233..2aa6666bde 100644 --- a/docs/tools/kompose/user-guide.md +++ b/docs/tools/kompose/user-guide.md @@ -572,4 +572,4 @@ Please note that changing service name might break some `docker-compose` files. Kompose supports Docker Compose versions: 1, 2 and 3. We have limited support on versions 2.1 and 3.2 due to their experimental nature. -A full list on compatibility between all three versions is listed in our [conversion document](/docs/conversion.md) including a list of all incompatible Docker Compose keys. +A full list on compatibility between all three versions is listed in our [conversion document](https://github.com/kubernetes/kompose/blob/master/docs/conversion.md) including a list of all incompatible Docker Compose keys.