From 0a1c0e36deabd05c453740a11a98cc5f795049e6 Mon Sep 17 00:00:00 2001 From: Daniele Paliotta Date: Tue, 11 Feb 2020 14:31:16 +0100 Subject: [PATCH] Fix typo --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0410bb0..2f68400 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ The exporters harvests metrics from the OpenVPN instance and exposes them for Pr These metrics are then fed to the [Prometheus Adapter](https://github.com/helm/charts/tree/master/stable/prometheus-adapter), which implements the k8s [Custom Metrics API](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-metrics-apis). The Adapter is reponsible for exposing the metrics through the k8s API, so that they can be queried by an HPA instance for autoscaling. -An high-level view of the components and their interactions is showed in the picture. +A high-level view of the components and their interactions is showed in the picture. ![](img/scheme.png) @@ -26,7 +26,7 @@ Everything was tested with: ## Installation We will first focus on provisioning the OpenVPN installation on top of Kubernetes. Once this is done, we will add the components that allow us to expose the metrics through Prometheus. -As we've seen, these metrics are then processed by the adapter and exposes through the k8s metrics API. +As we've seen, these metrics are then processed by the adapter and exposed through the k8s metrics API. After that, we can deploy HPA instances that autoscale against these new metrics.