Per review: drop the cross-namespace label-selector approach. Each app now
carries its own VMPodScrape next to its redis/valkey manifests, selecting on
the deployment's existing pod labels (mirroring the arrstack exportarr
pattern), so no opt-in monitoring.unkin.net/redis-exporter label is needed.
- Remove the monitoring.unkin.net/redis-exporter pod label from the
artifactapi/authentik/litellm redis and gitea/netbox valkey deployments
- Delete apps/base/observability/vmpodscrape-redis.yaml
- Add a local-namespace VMPodScrape (port metrics, path /metrics) to
artifactapi, authentik, litellm (app=redis), gitea (app=gitea-valkey),
netbox (app=netbox-valkey), and jellyfin (valkey-operator node labels)
No redis/valkey instance in the estate exports metrics today. Adds a
pinned redis_exporter (v1.89.0 via the artifactapi dockerhub remote)
next to every instance and two cluster-wide VMPodScrapes so the
observability VMAgent picks them all up.
- enables the valkey-operator exporter sidecar on the jellyfin
ValkeyCluster, overriding the operator's bare-dockerhub default image
with the artifactapi-proxied pin
- adds a metrics-exporter sidecar (:9121, port name metrics) to the
artifactapi/authentik/litellm redis and gitea/netbox valkey
Deployments, with the monitoring.unkin.net/redis-exporter opt-in pod
label
- adds VMPodScrape redis-exporters selecting that label in any
namespace, and VMPodScrape valkey-operator-clusters for
operator-managed pods whose labels are fixed (the ValkeyCluster CR has
no pod-label passthrough)
unkin-agent