Skip to content

Commit

Permalink
Fix typo
Browse files Browse the repository at this point in the history
  • Loading branch information
dpstart committed Feb 11, 2020
1 parent 406d920 commit 0a1c0e3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)

Expand All @@ -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.

Expand Down

0 comments on commit 0a1c0e3

Please sign in to comment.