dotbalo
ea46cbfc98
deploy prometheus by prometheus-operator
|
6 vuotta sitten | |
|---|---|---|
| .. | ||
| .gitignore | 6 vuotta sitten | |
| README.md | 6 vuotta sitten | |
| custom-metrics-apiserver-auth-delegator-cluster-role-binding.yaml | 6 vuotta sitten | |
| custom-metrics-apiserver-auth-reader-role-binding.yaml | 6 vuotta sitten | |
| custom-metrics-apiserver-deployment.yaml | 6 vuotta sitten | |
| custom-metrics-apiserver-resource-reader-cluster-role-binding.yaml | 6 vuotta sitten | |
| custom-metrics-apiserver-service-account.yaml | 6 vuotta sitten | |
| custom-metrics-apiserver-service.yaml | 6 vuotta sitten | |
| custom-metrics-apiservice.yaml | 6 vuotta sitten | |
| custom-metrics-cluster-role.yaml | 6 vuotta sitten | |
| custom-metrics-resource-reader-cluster-role.yaml | 6 vuotta sitten | |
| deploy.sh | 6 vuotta sitten | |
| gencerts.sh | 6 vuotta sitten | |
| hpa-custom-metrics-cluster-role-binding.yaml | 6 vuotta sitten | |
| teardown.sh | 6 vuotta sitten | |
README.md
Custom Metrics API
The custom metrics API allows the HPA v2 to scale on arbirary metrics.
This directory contains an example deployment of the custom metrics API adapter using Prometheus as the backing monitoring system.
In order to deploy the custom metrics adapter for Prometheus you need to generate TLS certficates used to serve the API. An example of how these could be generated can be found in ./gencerts.sh, note that this is not recommended to be used in production. You need to employ a secure PKI strategy, this is merely an example to get started and try it out quickly.
Once the generated Secret with the certificates is in place, you can deploy everything in the monitoring namespace using ./deploy.sh.
When you're done, you can teardown using the ./teardown.sh script.