From 908f40f5b898df6dc6653cd5ab220da2871ba9cd Mon Sep 17 00:00:00 2001 From: "Masaya Aoyama (@amsy810)" Date: Wed, 6 Jun 2018 05:42:56 +0900 Subject: [PATCH] "Getting started gce" deadlink (#8742) * Getting started gce deadlink 1. modify for kubernetes/website link 2. remove unnecessary .md link * modify link from github.com to kubernetes.io * revert blogs modification * revert blog post for meta char --- .../run-application/horizontal-pod-autoscale-walkthrough.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 cb7b4c8635..bc715cd627 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 @@ -21,7 +21,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. [Heapster](https://github.com/kubernetes/heapster) monitoring needs to be deployed in the cluster as Horizontal Pod Autoscaler uses it 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/getting-started-guides/gce), heapster monitoring will be turned-on by default). To specify multiple resource metrics for a Horizontal Pod Autoscaler, you must have a Kubernetes cluster