unkin-agent
13a04a6ebc
## Why No redis/valkey instance managed in this repo exports metrics today — the six caches (artifactapi, authentik, litellm, gitea, netbox, jellyfin) are blind spots in VictoriaMetrics. ## What - Enables the valkey-operator exporter sidecar on the jellyfin ValkeyCluster (`exporter.enabled: true`); overrides the operator's default bare-dockerhub image (`oliver006/redis_exporter:v1.80.0`) with the artifactapi-proxied pin. The operator manages a dedicated `_exporter` ACL user for it. - Adds a `metrics-exporter` sidecar (`artifactapi.k8s.syd1.au.unkin.net/dockerhub/oliver006/redis_exporter:v1.89.0`, :9121, port name `metrics`, req 32Mi/25m lim 64Mi/100m) to the five raw Deployments: artifactapi/authentik/litellm redis and gitea/netbox valkey. gitea/netbox sidecars get the same restrictive securityContext as their valkey container. - Adds the `monitoring.unkin.net/redis-exporter: "true"` opt-in pod label to all five pod templates. - Adds `apps/base/observability/vmpodscrape-redis.yaml` with two VMPodScrapes (any namespace, port `metrics`): `redis-exporters` selecting the opt-in label, and `valkey-operator-clusters` selecting `app.kubernetes.io/managed-by: valkey-operator` + `app.kubernetes.io/component: valkey-node` — the ValkeyCluster CR has no pod-label passthrough (verified against the v0.5.0 CRD/source), so operator pods cannot carry the opt-in label. ## Notes - No instance runs with `requirepass`/auth, so no REDIS_PASSWORD wiring is needed on the raw Deployments; the jellyfin exporter auth is operator-managed. - Validated: `kustomize build` on every touched base + au-syd1 overlay (helm overlays with `--enable-helm`) and `kubeconform -strict -ignore-missing-schemas` (68 valid, 0 invalid). Reviewed-on: #398 Co-authored-by: unkin-agent <unkin-agent@unkin.net> Co-committed-by: unkin-agent <unkin-agent@unkin.net>
50 lines
2.2 KiB
YAML
50 lines
2.2 KiB
YAML
---
|
|
# HA Valkey managed by valkey-operator as Jellyfin's distributed transcode-session
|
|
# store. shards:1 + replicas:2 is one primary with two replicas in a single shard
|
|
# group (three ValkeyNodes total): losing the primary triggers an automatic
|
|
# failover to a replica, so a node/pod loss no longer drops the shared transcode
|
|
# lease state the two Jellyfin replicas coordinate through. The operator always
|
|
# runs Valkey cluster-mode-enabled with protected-mode off and leaves the built-in
|
|
# `default` user passwordless, so clients connect with no auth/TLS (parity with the
|
|
# old open redis); StackExchange.Redis seeds off the single headless service and
|
|
# auto-discovers the topology plus failovers, so the connection string is
|
|
# unchanged. scheduling.node.spread.shard:Required renders pod anti-affinity that
|
|
# keeps the three nodes on distinct hosts (kubernetes.io/hostname), so one host
|
|
# loss removes at most one node. podDisruptionBudget.mode:Cluster lets the operator
|
|
# manage a quorum-aware PDB. Persistence stays omitted so /data is an emptyDir:
|
|
# lease state is ephemeral (30s TTLs), replication+failover already provide
|
|
# redundancy and a replaced node re-syncs from the primary, and an operator-managed
|
|
# PVC cannot carry the k8up.io/backup:"false" annotation the namespace's
|
|
# cluster-wide k8up Schedule needs to skip in-use RWO volumes.
|
|
apiVersion: valkey.io/v1alpha1
|
|
kind: ValkeyCluster
|
|
metadata:
|
|
name: jellyfin-valkey
|
|
namespace: jellyfin
|
|
spec:
|
|
shards: 1
|
|
replicas: 2
|
|
image: artifactapi.k8s.syd1.au.unkin.net/dockerhub/valkey/valkey:9.0.0
|
|
# redis_exporter sidecar (:9121, port name `metrics`) on every ValkeyNode pod;
|
|
# the operator manages a dedicated _exporter ACL user for it. Image overridden
|
|
# from the operator default (bare dockerhub oliver006/redis_exporter:v1.80.0)
|
|
# to the artifactapi-proxied pin. Scraped by the valkey-exporter VMPodScrape
|
|
# in vmpodscrape.yaml alongside this file.
|
|
exporter:
|
|
enabled: true
|
|
image: artifactapi.k8s.syd1.au.unkin.net/dockerhub/oliver006/redis_exporter:v1.89.0
|
|
scheduling:
|
|
node:
|
|
spread:
|
|
shard:
|
|
mode: Required
|
|
podDisruptionBudget:
|
|
mode: Cluster
|
|
resources:
|
|
requests:
|
|
cpu: 50m
|
|
memory: 128Mi
|
|
limits:
|
|
cpu: 500m
|
|
memory: 512Mi
|