proxmox-exporter 1.4.0 Helm chart
jhofer-cloudScored 14 Sept 2026
A Helm chart for Prometheus Proxmox VE Exporter ## Installation Create a secret with your Proxmox VE credentials: ```bash # Create the pve.yml file with your credentials cat > pve.yml << EOF default: user: prometheus@pve password: sEcr3T! verify_ssl: true # For multiple hosts with different credentials pve1: user: prometheus@pve token_name: "your-token-id-1" token_value: "your-token-value-1" verify_ssl: true pve2: user: prometheus@pve token_name: "your-token-id-2" token_value: "your-token-value-2" verify_ssl: true EOF # Create the Kubernetes secret kubectl create secret generic proxmox-credentials \ --from-file=pve.yml=./pve.yml -n your-namespace ``` ## Configuration ### Monitoring Multiple Proxmox Hosts To monitor multiple Proxmox hosts, configure the ServiceMonitor with multiple targets: ```yaml serviceMonitor: enabled: true extraLabels: release: prometheus targets: - name: pve1 url: 192.168.1.2 additionalMetricsRelabels: datacenter: dc1 - name: pve2 url: 192.168.1.3 additionalMetricsRelabels: datacenter: dc2 ``` ### External Secret Configuration The chart expects an external secret containing the Proxmox credentials. Configure the secret reference: ```yaml secretRef: name: "proxmox-credentials" key: "pve.yml" ``` The content of the secret should be in the format described in the Prometheus PVE Exporter documentation. For multiple hosts, configure your pve.yml with different modules: ```yaml default: user: prometheus@pve password: sEcr3T! verify_ssl: true pve1: user: prometheus@pve token_name: "your-token-id-1" token_value: "your-token-value-1" verify_ssl: true pve2: user: prometheus@pve token_name: "your-token-id-2" token_value: "your-token-value-2" verify_ssl: true ``` Then, in your ServiceMonitor configuration, specify which module to use for each target: ```yaml serviceMonitor: enabled: true module: default # Default module targets: - name: pve1 url: 192.168.1.2 - name: pve2 url: 192.168.1.3 # Override default module additionalMetricsRelabels: module: pve2 ``` ## Examples ### Basic installation with two Proxmox hosts ```yaml # values.yaml secretRef: name: "proxmox-credentials" key: "pve.yml" serviceMonitor: enabled: true extraLabels: release: prometheus targets: - name: pve1 url: 192.168.1.2 - name: pve2 url: 192.168.1.3 ``` ### Disabling specific collectors for large deployments ```yaml # values.yaml extraArgs: - "--no-collector.config" ``` ## Schema For now it only has a simple schema generated with: ```bash helm schema . --no-dependencies -k additionalProperties -k required ```
Version 1.4.0 1 month agoapp version 3.10.0 0Artifact Hub
proxmox-exporter 1.4.0 deploys 1 container image: prompve/prometheus-pve-exporter. Across them, 28 findings — 0 critical, 0 high. The highest contribution is ALPINE-CVE-2026-63073 in openssl 3.5.7-r0, fixed in 3.5.8-r0.
Radar Score
Radar Score is the sum of every finding’s contribution; the colour is the worst finding’s band.
Container images
| Image | Tag | Vulnerabilities | Radar Score |
|---|---|---|---|
| prompve/ | 3.10.0 | 00721 | 348 |
Rendered with the chart’s default values for linux/amd64. Optional subcharts, images set by operator flags and images inside CRD payloads are not seen and are counted as unmeasured.
Medium findings
Medium: findings whose contribution to the Radar Score is 15–39. Show every band
| Severity | Advisory | Package | Fixed in |
|---|---|---|---|
| Medium | ALPINE-CVE-2026-63073 | openssl | 3.5.8-r0 |
| Medium | ALPINE-CVE-2026-18798 | openssl | 3.5.8-r0 |
| Medium | ALPINE-CVE-2026-63076 | openssl | 3.5.8-r0 |
| Medium | ALPINE-CVE-2026-14457 | openssl | 3.5.8-r0 |
| Medium | ALPINE-CVE-2026-66046 | expat | 2.8.4-r0 |
| Medium | ALPINE-CVE-2026-9669 | python3 | 3.14.7-r0 |
| Medium | ALPINE-CVE-2026-11940 | python3 | 3.14.7-r0 |
Indexed versions
The latest version and the previous major, as selected nightly from the repository’s index.
README badge
Markdown. The badge shows the latest version’s band and Radar Score, refreshed daily.