From 18ccf430215dcc3c05fc9183df2f51b21479934c Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Thu, 18 May 2017 18:16:31 -0700 Subject: [PATCH] Update link: user-guide/application-troubleshooting. (#3834) --- docs/admin/federation/index.md | 2 +- docs/concepts/workloads/controllers/deployment.md | 2 +- docs/getting-started-guides/rkt/index.md | 2 +- docs/tasks/administer-cluster/cpu-memory-limit.md | 2 +- docs/tasks/debug-application-cluster/debug-cluster.md | 2 +- docs/tools/kompose/user-guide.md | 2 +- docs/tutorials/stateless-application/hello-minikube.md | 2 +- docs/user-guide/docker-cli-to-kubectl.md | 2 +- docs/user-guide/walkthrough/k8s201.md | 2 +- 9 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/admin/federation/index.md b/docs/admin/federation/index.md index b87fd45775..4407267af6 100644 --- a/docs/admin/federation/index.md +++ b/docs/admin/federation/index.md @@ -129,7 +129,7 @@ $ federation/deploy/deploy.sh deploy_federation ``` This spins up the federation control components as pods managed by -[`Deployments`](http://kubernetes.io/docs/user-guide/deployments/) on your +[`Deployments`](/docs/concepts/workloads/controllers/deployment/) on your existing Kubernetes cluster. It also starts a [`type: LoadBalancer`](http://kubernetes.io/docs/user-guide/services/#type-loadbalancer) [`Service`](http://kubernetes.io/docs/user-guide/services/) for the diff --git a/docs/concepts/workloads/controllers/deployment.md b/docs/concepts/workloads/controllers/deployment.md index 0ab40130c5..6ca73561a2 100644 --- a/docs/concepts/workloads/controllers/deployment.md +++ b/docs/concepts/workloads/controllers/deployment.md @@ -231,7 +231,7 @@ before changing course. Sometimes you may want to rollback a Deployment; for example, when the Deployment is not stable, such as crash looping. By default, all of the Deployment's rollout history is kept in the system so that you can rollback anytime you want -(you can change that by modifying [revision history limit](/docs/user-guide/deployments/#revision-history-limit)). +(you can change that by modifyingrevision history limit]). **Note:** a Deployment's revision is created when a Deployment's rollout is triggered. This means that the new revision is created if and only if the Deployment's pod template (i.e. `.spec.template`) is changed, diff --git a/docs/getting-started-guides/rkt/index.md b/docs/getting-started-guides/rkt/index.md index 3df9c0070f..a5d87af58f 100644 --- a/docs/getting-started-guides/rkt/index.md +++ b/docs/getting-started-guides/rkt/index.md @@ -222,4 +222,4 @@ By default, the log verbosity level is 2. In order to see more log messages rela ### Check Kubernetes events and logs. -Kubernetes provides various tools for troubleshooting and examination. More information can be found [in the app troubleshooting guide](/docs/user-guide/application-troubleshooting). +Kubernetes provides various tools for troubleshooting and examination. More information can be found [in the app troubleshooting guide](/docs/tasks/debug-application-cluster/debug-application/). diff --git a/docs/tasks/administer-cluster/cpu-memory-limit.md b/docs/tasks/administer-cluster/cpu-memory-limit.md index 865cb48562..415f357808 100644 --- a/docs/tasks/administer-cluster/cpu-memory-limit.md +++ b/docs/tasks/administer-cluster/cpu-memory-limit.md @@ -94,7 +94,7 @@ were previously created in a namespace. If a resource (CPU or memory) is being restricted by a limit, the user will get an error at time of creation explaining why. -Let's first spin up a [Deployment](/docs/user-guide/deployments) that creates a single container Pod to demonstrate +Let's first spin up a [Deployment](/docs/concepts/workloads/controllers/deployment/) that creates a single container Pod to demonstrate how default values are applied to each pod. ```shell diff --git a/docs/tasks/debug-application-cluster/debug-cluster.md b/docs/tasks/debug-application-cluster/debug-cluster.md index 7e11eb12b0..a1c867394d 100644 --- a/docs/tasks/debug-application-cluster/debug-cluster.md +++ b/docs/tasks/debug-application-cluster/debug-cluster.md @@ -6,7 +6,7 @@ title: Troubleshooting Clusters This doc is about cluster troubleshooting; we assume you have already ruled out your application as the root cause of the problem you are experiencing. See -the [application troubleshooting guide](/docs/user-guide/application-troubleshooting) for tips on application debugging. +the [application troubleshooting guide]/docs/tasks/debug-application-cluster/debug-application) for tips on application debugging. You may also visit [troubleshooting document](/docs/troubleshooting/) for more information. ## Listing your cluster diff --git a/docs/tools/kompose/user-guide.md b/docs/tools/kompose/user-guide.md index 8a3683a229..aa95c02be0 100644 --- a/docs/tools/kompose/user-guide.md +++ b/docs/tools/kompose/user-guide.md @@ -284,7 +284,7 @@ Note: ## Alternate formats -The default `kompose` transformation will generate Kubernetes [Deployments](http://kubernetes.io/docs/user-guide/deployments/) and [Services](http://kubernetes.io/docs/user-guide/services/), in yaml format. You have alternative option to generate json with `-j`. Also, you can alternatively generate [Replication Controllers](http://kubernetes.io/docs/user-guide/replication-controller/) objects, [Deamon Sets](http://kubernetes.io/docs/admin/daemons/), or [Helm](https://github.com/helm/helm) charts. +The default `kompose` transformation will generate Kubernetes [Deployments](/docs/concepts/workloads/controllers/deployment/) and [Services](http://kubernetes.io/docs/user-guide/services/), in yaml format. You have alternative option to generate json with `-j`. Also, you can alternatively generate [Replication Controllers](http://kubernetes.io/docs/user-guide/replication-controller/) objects, [Deamon Sets](http://kubernetes.io/docs/admin/daemons/), or [Helm](https://github.com/helm/helm) charts. ```console $ kompose convert -j diff --git a/docs/tutorials/stateless-application/hello-minikube.md b/docs/tutorials/stateless-application/hello-minikube.md index e755675976..cb669af767 100644 --- a/docs/tutorials/stateless-application/hello-minikube.md +++ b/docs/tutorials/stateless-application/hello-minikube.md @@ -164,7 +164,7 @@ Now the Minikube VM can run the image you built. A Kubernetes [*Pod*](/docs/concepts/workloads/pods/pod/) is a group of one or more Containers, tied together for the purposes of administration and networking. The Pod in this tutorial has only one Container. A Kubernetes -[*Deployment*](/docs/user-guide/deployments) checks on the health of your +[*Deployment*](/docs/concepts/workloads/controllers/deployment/) checks on the health of your Pod and restarts the Pod's Container if it terminates. Deployments are the recommended way to manage the creation and scaling of Pods. diff --git a/docs/user-guide/docker-cli-to-kubectl.md b/docs/user-guide/docker-cli-to-kubectl.md index d2fbd40240..127d5dd6ed 100644 --- a/docs/user-guide/docker-cli-to-kubectl.md +++ b/docs/user-guide/docker-cli-to-kubectl.md @@ -43,7 +43,7 @@ $ kubectl expose deployment nginx-app --port=80 --name=nginx-http service "nginx-http" exposed ``` -With kubectl, we create a [Deployment](/docs/user-guide/deployments) which will make sure that N pods are running nginx (where N is the number of replicas stated in the spec, which defaults to 1). We also create a [service](/docs/user-guide/services) with a selector that matches the Deployment's selector. See the [Quick start](/docs/user-guide/quick-start) for more information. +With kubectl, we create a [Deployment](/docs/concepts/workloads/controllers/deployment/) which will make sure that N pods are running nginx (where N is the number of replicas stated in the spec, which defaults to 1). We also create a [service](/docs/user-guide/services) with a selector that matches the Deployment's selector. See the [Quick start](/docs/user-guide/quick-start) for more information. By default images are run in the background, similar to `docker run -d ...`, if you want to run things in the foreground, use: diff --git a/docs/user-guide/walkthrough/k8s201.md b/docs/user-guide/walkthrough/k8s201.md index 5c56832a21..411b396e78 100644 --- a/docs/user-guide/walkthrough/k8s201.md +++ b/docs/user-guide/walkthrough/k8s201.md @@ -54,7 +54,7 @@ They are a core concept used by two additional Kubernetes building blocks: Deplo Now that you know how to make awesome, multi-container, labeled Pods and you want to use them to build an application, you might be tempted to just start building a whole bunch of individual Pods, but if you do that, a whole host of operational concerns pop up. For example: how will you scale the number of Pods up or down? How will you roll out a new release? -The answer to those questions and more is to use a [_Deployment_](/docs/user-guide/deployments/#what-is-a-deployment) to manage maintaining and updating your running _Pods_. +The answer to those questions and more is to use a [Deployment](/docs/concepts/workloads/controllers/deployment/) to manage maintaining and updating your running _Pods_. A Deployment object defines a Pod creation template (a "cookie-cutter" if you will) and desired replica count. The Deployment uses a label selector to identify the Pods it manages, and will create or delete Pods as needed to meet the replica count. Deployments are also used to manage safely rolling out changes to your running Pods.