9b154d38f4
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)
20 lines
664 B
YAML
20 lines
664 B
YAML
---
|
|
# Scrape the operator-injected redis_exporter sidecar (:9121, port name
|
|
# `metrics`) on the jellyfin-valkey ValkeyNode pods. The valkey-operator gives
|
|
# its pods fixed labels only (no pod-label passthrough on the ValkeyCluster CR),
|
|
# so select on the operator-managed labels. Picked up by the observability
|
|
# VMAgent (selectAllByDefault).
|
|
apiVersion: operator.victoriametrics.com/v1beta1
|
|
kind: VMPodScrape
|
|
metadata:
|
|
name: valkey-exporter
|
|
namespace: jellyfin
|
|
spec:
|
|
selector:
|
|
matchLabels:
|
|
app.kubernetes.io/managed-by: valkey-operator
|
|
app.kubernetes.io/component: valkey-node
|
|
podMetricsEndpoints:
|
|
- port: metrics
|
|
path: /metrics
|