From 31ed65dbe3c797f9effd16a47801820f15472580 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Wed, 4 Oct 2017 18:25:57 -0700 Subject: [PATCH] Update links to avoid redirects. (#5771) --- .../cluster-administration-overview.md | 4 ++-- docs/concepts/configuration/secret.md | 4 ++-- .../services-networking/connect-applications-service.md | 6 +----- docs/getting-started-guides/cloudstack.md | 2 +- docs/setup/independent/create-cluster-kubeadm.md | 4 ++-- docs/tasks/administer-cluster/limit-storage-consumption.md | 2 +- docs/tasks/administer-cluster/securing-a-cluster.md | 4 ++-- docs/tasks/debug-application-cluster/monitor-node-health.md | 2 +- 8 files changed, 12 insertions(+), 16 deletions(-) diff --git a/docs/concepts/cluster-administration/cluster-administration-overview.md b/docs/concepts/cluster-administration/cluster-administration-overview.md index ec41426044..4fe1feaef5 100644 --- a/docs/concepts/cluster-administration/cluster-administration-overview.md +++ b/docs/concepts/cluster-administration/cluster-administration-overview.md @@ -7,7 +7,7 @@ title: Cluster Administration Overview {% capture overview %} The cluster administration overview is for anyone creating or administering a Kubernetes cluster. -It assumes some familiarity with concepts in the [User Guide](/docs/user-guide/). +It assumes some familiarity with core Kubernetes [concepts](/docs/concepts/). {% endcapture %} {% capture body %} @@ -18,7 +18,7 @@ See the guides in [Picking the Right Solution](/docs/setup/pick-right-solution/) Before choosing a guide, here are some considerations: - Do you just want to try out Kubernetes on your computer, or do you want to build a high-availability, multi-node cluster? Choose distros best suited for your needs. - - **If you are designing for high-availability**, learn about configuring [clusters in multiple zones](/docs/admin/multi-cluster/). + - **If you are designing for high-availability**, learn about configuring [clusters in multiple zones](/docs/concepts/cluster-administration/federation/). - Will you be using **a hosted Kubernetes cluster**, such as [Google Container Engine (GKE)](https://cloud.google.com/container-engine/), or **hosting your own cluster**? - Will your cluster be **on-premises**, or **in the cloud (IaaS)**? Kubernetes does not directly support hybrid clusters. Instead, you can set up multiple clusters. - **If you are configuring Kubernetes on-premises**, consider which [networking model](/docs/concepts/cluster-administration/networking/) fits best. One option for custom networking is [*OpenVSwitch GRE/VxLAN networking*](/docs/admin/ovs-networking/), which uses OpenVSwitch to set up networking between pods across Kubernetes nodes. diff --git a/docs/concepts/configuration/secret.md b/docs/concepts/configuration/secret.md index 70e7c2d03e..e0eb74301a 100644 --- a/docs/concepts/configuration/secret.md +++ b/docs/concepts/configuration/secret.md @@ -37,7 +37,7 @@ The automatic creation and use of API credentials can be disabled or overridden if desired. However, if all you need to do is securely access the apiserver, this is the recommended workflow. -See the [Service Account](/docs/user-guide/service-accounts) documentation for more +See the [Service Account](/docs/tasks/configure-pod-container/configure-service-account/) documentation for more information on how Service Accounts work. ### Creating your own Secrets @@ -406,7 +406,7 @@ See [Adding ImagePullSecrets to a service account](/docs/tasks/configure-pod-con Manually created secrets (e.g. one containing a token for accessing a github account) can be automatically attached to pods based on their service account. -See [Injecting Information into Pods Using a PodPreset](/docs/tasks/run-application/podpreset/) for a detailed explanation of that process. +See [Injecting Information into Pods Using a PodPreset](/docs/tasks/inject-data-application/podpreset/) for a detailed explanation of that process. ## Details diff --git a/docs/concepts/services-networking/connect-applications-service.md b/docs/concepts/services-networking/connect-applications-service.md index 7079cfbeea..1308d8bc0b 100644 --- a/docs/concepts/services-networking/connect-applications-service.md +++ b/docs/concepts/services-networking/connect-applications-service.md @@ -168,7 +168,7 @@ Till now we have only accessed the nginx server from within the cluster. Before * Self signed certificates for https (unless you already have an identity certificate) * An nginx server configured to use the certificates -* A [secret](/docs/user-guide/secrets) that makes the certificates accessible to pods +* A [secret](/docs/concepts/configuration/secret/) that makes the certificates accessible to pods You can acquire all these from the [nginx https example](https://github.com/kubernetes/examples/tree/{{page.githubbranch}}/staging/https-nginx/), in short: @@ -296,7 +296,3 @@ clusters and cloud providers, to provide increased availability, better fault tolerance and greater scalability for your services. See the [Federated Services User Guide](/docs/concepts/cluster-administration/federation-service-discovery/) for further information. - -## What's next? - -[Learn about more Kubernetes features that will help you run containers reliably in production.](/docs/user-guide/production-pods) diff --git a/docs/getting-started-guides/cloudstack.md b/docs/getting-started-guides/cloudstack.md index c0d0263e60..d92b90b2eb 100644 --- a/docs/getting-started-guides/cloudstack.md +++ b/docs/getting-started-guides/cloudstack.md @@ -92,6 +92,6 @@ SSH to it using the key that was created and using the _core_ user and you can l IaaS Provider | Config. Mgmt | OS | Networking | Docs | Conforms | Support Level -------------------- | ------------ | ------ | ---------- | --------------------------------------------- | ---------| ---------------------------- -CloudStack | Ansible | CoreOS | flannel | [docs](/docs/getting-started-guides/cloudstack) | | Community ([@Guiques](https://github.com/ltupin/)) +CloudStack | Ansible | CoreOS | flannel | [docs](/docs/getting-started-guides/cloudstack/) | | Community ([@Guiques](https://github.com/ltupin/)) For support level information on all solutions, see the [Table of solutions](/docs/getting-started-guides/#table-of-solutions) chart. diff --git a/docs/setup/independent/create-cluster-kubeadm.md b/docs/setup/independent/create-cluster-kubeadm.md index bc1a9fc96a..ac9f39eed2 100644 --- a/docs/setup/independent/create-cluster-kubeadm.md +++ b/docs/setup/independent/create-cluster-kubeadm.md @@ -18,7 +18,7 @@ This process works with local VMs, physical servers and/or cloud servers. It is simple enough that you can easily integrate its use into your own automation (Terraform, Chef, Puppet, etc). -See the full [kubeadm reference](/docs/admin/kubeadm) for information on all +See the full [kubeadm reference](/docs/admin/kubeadm/) for information on all kubeadm command-line flags and for advice on automating kubeadm itself. kubeadm assumes you have a set of machines (virtual or real) that are up and @@ -121,7 +121,7 @@ will then download and install the cluster database and control plane components. This may take several minutes. You can't run `kubeadm init` twice without tearing down the cluster in between -([unless you're upgrading from v1.6 to v1.7](/docs/tasks/administer-cluster/kubeadm-upgrade-1-7)), +([unless you're upgrading from v1.6 to v1.7](/docs/tasks/administer-cluster/kubeadm-upgrade-1-7/)), see [Tear Down](#tear-down). The output should look like: diff --git a/docs/tasks/administer-cluster/limit-storage-consumption.md b/docs/tasks/administer-cluster/limit-storage-consumption.md index 018ff996c3..fd18f2a7bb 100644 --- a/docs/tasks/administer-cluster/limit-storage-consumption.md +++ b/docs/tasks/administer-cluster/limit-storage-consumption.md @@ -7,7 +7,7 @@ title: Limit Storage Consumption This example demonstrates an easy way to limit the amount of storage consumed in a namespace. The following resources are used in the demonstration: [ResourceQuota](/docs/concepts/policy/resource-quotas/), -[LimitRange](/docs/tasks/configure-pod-container/limit-range/), +[LimitRange](/docs/tasks/administer-cluster/memory-default-namespace/), and [PersistentVolumeClaim](/docs/concepts/storage/persistent-volumes/). {% endcapture %} diff --git a/docs/tasks/administer-cluster/securing-a-cluster.md b/docs/tasks/administer-cluster/securing-a-cluster.md index b967a01138..70645afcb5 100644 --- a/docs/tasks/administer-cluster/securing-a-cluster.md +++ b/docs/tasks/administer-cluster/securing-a-cluster.md @@ -123,7 +123,7 @@ prevent cross talk, or advanced networking policy. By default, there are no restrictions on which nodes may run a pod. Kubernetes offers a [rich set of policies for controlling placement of pods onto nodes](/docs/concepts/configuration/assign-pod-node/) -and the [taint based pod placement and eviction](/docs/concepts/configuration/taint-and-toleration) +and the [taint based pod placement and eviction](/docs/concepts/configuration/taint-and-toleration/) that are available to end users. For many clusters use of these policies to separate workloads can be a convention that authors adopt or enforce via tooling. @@ -151,7 +151,7 @@ access to a subset of the keyspace is strongly recommended. ### Enable audit logging -The [audit logger](/docs/admin/audit/) is an alpha feature that records actions taken by the +The [audit logger](/docs/tasks/debug-application-cluster/audit/) is an alpha feature that records actions taken by the API for later analysis in the event of a compromise. It is recommended to enable audit logging and archive the audit file on a secure server. diff --git a/docs/tasks/debug-application-cluster/monitor-node-health.md b/docs/tasks/debug-application-cluster/monitor-node-health.md index cbe5c1b9e4..0faad52a33 100644 --- a/docs/tasks/debug-application-cluster/monitor-node-health.md +++ b/docs/tasks/debug-application-cluster/monitor-node-health.md @@ -32,7 +32,7 @@ kernel log now. It doesn't support log tools like journald. * The kernel issue detection of node problem detector has assumption on kernel log format, and now it only works on Ubuntu and Debian. However, it is easy to extend -it to [support other log format](/docs/admin/node-problem/#support-other-log-format). +it to [support other log format](/docs/tasks/debug-application-cluster/monitor-node-health/#support-other-log-format). ## Enable/Disable in GCE cluster