From 0a555bdab33a965b9d0bc66e19d24cf8faa9b7b9 Mon Sep 17 00:00:00 2001 From: Steve Waterworth Date: Wed, 22 May 2019 16:06:28 +0100 Subject: [PATCH] move script --- K8s/{autoscaling => }/autoscale.sh | 0 load-gen/README.md | 4 ++-- 2 files changed, 2 insertions(+), 2 deletions(-) rename K8s/{autoscaling => }/autoscale.sh (100%) diff --git a/K8s/autoscaling/autoscale.sh b/K8s/autoscale.sh similarity index 100% rename from K8s/autoscaling/autoscale.sh rename to K8s/autoscale.sh diff --git a/load-gen/README.md b/load-gen/README.md index c2bcda9..91283ce 100644 --- a/load-gen/README.md +++ b/load-gen/README.md @@ -40,7 +40,7 @@ To run the load test in Kubernetes, apply the `K8s/load-deployment.yaml` configu $ kubectl -n robot-shop apply -f K8s/load-deployment.yaml ``` -If you want to enable auto-scaling on relevant components (non-databases), just run the script in the autoscaling directory. However you will first need to make sure a [metrics-server](https://kubernetes.io/docs/tasks/debug-application-cluster/resource-metrics-pipeline/) is running in your cluster, enabling the Horizontal Pod Autoscaler to know about the CPU and memory usage of the pods. From Kubernetes version 1.8 a `metrics-serer` deployment should be configured by default, run the command below to check. +If you want to enable auto-scaling on relevant components (non-databases), just run the script in the autoscaling directory. However you will first need to make sure a [metrics-server](https://kubernetes.io/docs/tasks/debug-application-cluster/resource-metrics-pipeline/) is running in your cluster, this enables the Horizontal Pod Autoscaler to know about the CPU and memory usage of the pods. From Kubernetes version 1.8, a `metrics-serer` deployment should be configured by default, run the command below to check. ```shell $ kubectl -n kube-system get deployment @@ -49,6 +49,6 @@ $ kubectl -n kube-system get deployment The autoscaling is installed with: ```shell -$ K8s/autoscaling/autoscale.sh +$ K8s/autoscale.sh ```