From 5638a38d784902c8c91039fd606e048db1f248f2 Mon Sep 17 00:00:00 2001 From: Kai Chen Date: Fri, 13 Jul 2018 12:23:27 -0700 Subject: [PATCH] Fix doc references to Kubernetes services provided by AWS, Azure and GCE --- content/en/docs/setup/scratch.md | 6 +++--- content/en/docs/setup/turnkey/gce.md | 4 ++-- content/en/docs/setup/turnkey/stackpoint.md | 6 +++--- .../run-application/horizontal-pod-autoscale-walkthrough.md | 2 +- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/content/en/docs/setup/scratch.md b/content/en/docs/setup/scratch.md index 77871e8a7515f..ac7b6d6fbcf5e 100644 --- a/content/en/docs/setup/scratch.md +++ b/content/en/docs/setup/scratch.md @@ -90,7 +90,7 @@ to implement one of the above options: - You can also write your own. - **Compile support directly into Kubernetes** - This can be done by implementing the "Routes" interface of a Cloud Provider module. - - The Google Compute Engine ([GCE](/docs/getting-started-guides/gce/)) and [AWS](/docs/getting-started-guides/aws/) guides use this approach. + - The Google Compute Engine ([GCE](/docs/setup/turnkey/gce/)) and [AWS](/docs/setup/turnkey/aws/) guides use this approach. - **Configure the network external to Kubernetes** - This can be done by manually running commands, or through a set of externally maintained scripts. - You have to implement this yourself, but it can give you an extra degree of flexibility. @@ -851,7 +851,7 @@ Cluster validation succeeded ### Inspect pods and services -Try to run through the "Inspect your cluster" section in one of the other Getting Started Guides, such as [GCE](/docs/getting-started-guides/gce/#inspect-your-cluster). +Try to run through the "Inspect your cluster" section in one of the other Getting Started Guides, such as [GCE](/docs/setup/turnkey/gce/#inspect-your-cluster). You should see some services. You should also see "mirror pods" for the apiserver, scheduler and controller-manager, plus any add-ons you started. ### Try Examples @@ -869,7 +869,7 @@ pinging or SSH-ing from one node to another. ### Getting Help -If you run into trouble, please see the section on [troubleshooting](/docs/getting-started-guides/gce/#troubleshooting), post to the +If you run into trouble, please see the section on [troubleshooting](/docs/setup/turnkey/gce/#troubleshooting), post to the [kubernetes-users group](https://groups.google.com/forum/#!forum/kubernetes-users), or come ask questions on [Slack](/docs/troubleshooting#slack). ## Support Level diff --git a/content/en/docs/setup/turnkey/gce.md b/content/en/docs/setup/turnkey/gce.md index 063069e4a8b5a..4f3c7045ca853 100644 --- a/content/en/docs/setup/turnkey/gce.md +++ b/content/en/docs/setup/turnkey/gce.md @@ -63,7 +63,7 @@ cluster/kube-up.sh If you want more than one cluster running in your project, want to use a different name, or want a different number of worker nodes, see the `/cluster/gce/config-default.sh` file for more fine-grained configuration before you start up your cluster. -If you run into trouble, please see the section on [troubleshooting](/docs/getting-started-guides/gce/#troubleshooting), post to the +If you run into trouble, please see the section on [troubleshooting](/docs/setup/turnkey/gce/#troubleshooting), post to the [kubernetes-users group](https://groups.google.com/forum/#!forum/kubernetes-users), or come ask questions on [Slack](/docs/troubleshooting/#slack). The next few steps will show you: @@ -206,7 +206,7 @@ field values: IaaS Provider | Config. Mgmt | OS | Networking | Docs | Conforms | Support Level -------------------- | ------------ | ------ | ---------- | --------------------------------------------- | ---------| ---------------------------- -GCE | Saltstack | Debian | GCE | [docs](/docs/getting-started-guides/gce/) | | Project +GCE | Saltstack | Debian | GCE | [docs](/docs/setup/turnkey/gce/) | | Project For support level information on all solutions, see the [Table of solutions](/docs/getting-started-guides/#table-of-solutions) chart. diff --git a/content/en/docs/setup/turnkey/stackpoint.md b/content/en/docs/setup/turnkey/stackpoint.md index a0a108bb30332..da6f64ffcf539 100644 --- a/content/en/docs/setup/turnkey/stackpoint.md +++ b/content/en/docs/setup/turnkey/stackpoint.md @@ -37,7 +37,7 @@ Choose any extra options you may want to include with your cluster, then click * You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters). -For information on using and managing a Kubernetes cluster on AWS, [consult the Kubernetes documentation](/docs/getting-started-guides/aws/). +For information on using and managing a Kubernetes cluster on AWS, [consult the Kubernetes documentation](/docs/setup/turnkey/aws/). @@ -69,7 +69,7 @@ Choose any extra options you may want to include with your cluster, then click * You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters). -For information on using and managing a Kubernetes cluster on GCE, [consult the Kubernetes documentation](/docs/getting-started-guides/gce/). +For information on using and managing a Kubernetes cluster on GCE, [consult the Kubernetes documentation](/docs/setup/turnkey/gce/). @@ -164,7 +164,7 @@ Choose any extra options you may want to include with your cluster, then click * You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters). -For information on using and managing a Kubernetes cluster on Azure, [consult the Kubernetes documentation](/docs/getting-started-guides/azure/). +For information on using and managing a Kubernetes cluster on Azure, [consult the Kubernetes documentation](/docs/setup/turnkey/azure/). diff --git a/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md b/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md index 7d93e432ce4c8..d6dc3b0a02377 100644 --- a/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md +++ b/content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md @@ -27,7 +27,7 @@ This document walks you through an example of enabling Horizontal Pod Autoscaler This example requires a running Kubernetes cluster and kubectl, version 1.2 or later. [metrics-server](https://github.com/kubernetes/heapster) monitoring needs to be deployed in the cluster to provide metrics via the resource metrics API, as Horizontal Pod Autoscaler uses this API to collect metrics -(if you followed [getting started on GCE guide](/docs/getting-started-guides/gce.md), +(if you followed [getting started on GCE guide](/docs/setup/turnkey/gce/), metrics-server monitoring will be turned-on by default). To specify multiple resource metrics for a Horizontal Pod Autoscaler, you must have a Kubernetes cluster