chore(deps): update dependency volker.raschek/prometheus-fail2ban-exporter-charts to v0.4.25 #108

Merged
CSRBot merged 1 commits from renovate/volker.raschek-prometheus-fail2ban-exporter-charts-0.x into master 2026-05-03 20:17:21 +02:00

View File

@@ -35,7 +35,7 @@ separate [chapter](#argocd).
```bash
helm repo add prometheus-exporters https://git.cryptic.systems/api/packages/volker.raschek/helm
helm repo update
CHART_VERSION=0.4.23
CHART_VERSION=0.4.25
helm install --version "${CHART_VERSION}" prometheus-fail2ban-exporter prometheus-exporters/prometheus-fail2ban-exporter \
--set 'prometheus.metrics.enabled=true' \
--set 'prometheus.metrics.serviceMonitor.enabled=true'
@@ -59,7 +59,7 @@ version of the chart must be in sync with the `values.yaml`. Newer *minor* versi
versions can break something!
```bash
CHART_VERSION=0.4.23
CHART_VERSION=0.4.25
helm show values --version "${CHART_VERSION}" prometheus-exporters/prometheus-fail2ban-exporter > values.yaml
```
@@ -97,7 +97,7 @@ Further information about this topic can be found in one of Kanishk's blog
> Please take care the a CPU limit < `1000m` can also lead to CPU throttling. Please read the linked documentation carefully.
```bash
CHART_VERSION=0.4.23
CHART_VERSION=0.4.25
helm install --version "${CHART_VERSION}" prometheus-fail2ban-exporter prometheus-exporters/prometheus-fail2ban-exporter \
--set 'prometheus.metrics.enabled=true' \
--set 'prometheus.metrics.serviceMonitor.enabled=true' \
@@ -115,7 +115,7 @@ the Grafana container file system so that it is subsequently available to the us
makes this possible.
```bash
CHART_VERSION=0.4.23
CHART_VERSION=0.4.25
helm install --version "${CHART_VERSION}" prometheus-fail2ban-exporter prometheus-exporters/prometheus-fail2ban-exporter \
--set 'grafana.enabled=true'
```