be2584fd7c
Prometheus documentation shows that /-/ready can be used to check that it is ready to service traffic (i.e. respond to queries) [0]. I've witnessed cases where Prometheus's readiness probe is passing during initial deployment using /status, which in turn triggers its helm test to start. Said helm test then fails because /status is not a good a reliable indicator that Prometheus is actually ready to serve traffic and the helm test is performing actions that require it to be proprely up and ready. [0]: https://prometheus.io/docs/prometheus/latest/management_api/ Change-Id: Iab22d0c986d680663fbe8e84d6c0d89b03dc6428
13 lines
460 B
YAML
13 lines
460 B
YAML
---
|
|
prometheus:
|
|
- 0.1.0 Initial Chart
|
|
- 0.1.1 Change helm-toolkit dependency version to ">= 0.1.0"
|
|
- 0.1.2 Add configurable readiness/liveness Probes
|
|
- 0.1.3 Revert "Render Rules as Templates"
|
|
- 0.1.4 Fix spacing inconsistencies with flags
|
|
- 0.1.5 Fix spacing inconsistencies with flags
|
|
- 0.1.6 Upgrade version to v2.25 fix/remove deprecated flags
|
|
- 0.1.7 Enable TLS for Prometheus
|
|
- 0.1.8 Change readiness probe from /status to /-/ready
|
|
...
|