aa3efe9715
This change adds feature to launch Prometheus process using a custom script which should be stored in override values. Because the known issue https://github.com/prometheus/prometheus/issues/6934 is still open many years, we are going to struggle with growing WAL files using our custom downstream wrapper script which stops Prometheus process and deletes WALs. This solution can not fit all customers because completely kills wal cached data but it is ok for our purposes. Such way I just added the feature to use another custom script to launch Prometheus and left original functionality by default. Default/custom mode are defined in 'values.yaml' as the body of the custom launcher script. Change-Id: Ie02ea1d6a7de5c676e2e96f3dcd6aca172af4afb
19 lines
765 B
YAML
19 lines
765 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
|
|
- 0.1.9 Retrieve backend port name from values.yaml
|
|
- 0.1.10 Use full image ref for docker official images
|
|
- 0.1.11 Update htk requirements
|
|
- 0.1.12 Update default image value to Wallaby
|
|
- 0.1.13 Added OCI registry authentication
|
|
- 0.1.14 Added feature to launch Prometheus with custom script
|
|
...
|