TODO: Fix CNPG postgres metrics exporter (port 9187 not listening)
CNPG Cluster
pal-e-postgres has enablePodMonitor: true and customQueriesConfigMap: cnpg-default-monitoring, and the PodMonitor exists, but the metrics exporter never starts on port 9187. Port is declared in the pod spec but nothing binds to it — even after a fresh pod restart.Instance image:
ghcr.io/cloudnative-pg/postgresql:17.4-1Operator version: 1.28.1
Listening ports: 5432 (postgres), 8010 (instance manager). 9187 absent.
Impact: Permanent TargetDown alert for
postgres/pal-e-postgres.Options:
- Investigate CNPG docs for exporter requirements at this version
- Check if operator upgrade (1.28.x → 1.29+) fixes it
- Disable PodMonitor (
enablePodMonitor: false) as a quick silence
Source:
phase-platform-16-alert-tuning (16e investigation)Investigation (2026-03-17): Port 9187 IS listening and serving valid Prometheus metrics over HTTP. The problem is the auto-generated PodMonitor from
enablePodMonitor: true was being dropped by Prometheus (807 dropped targets). enablePodMonitor is deprecated in CNPG 1.28 and will be removed. Fix: PR opened to replace with manual PodMonitor kubernetes_manifest resource with proper selector labels. The metrics endpoint serves HTTP (not HTTPS), so no TLS config needed in the PodMonitor.