redis-to-valkey

# redis-to-valkey Migrate Redis (Bitnami-chart Sentinel HA or any standalone/replicated Redis) to Valkey on Kubernetes with data intact, clients reconnected, and no dependency left on dead-ended Bitnami artifacts. Facts below were verified 2026-07-18 against primary sources (valkey source at release tags, chart repos, vendor docs); re-verify anything version-gated before relying on it in a later year. ## Why this migration exists Broadcom locked down the free Bitnami catalog (effective 2025-09-29): versioned images moved to frozen `docker.io/bitnamilegacy` and most charts froze. `charts.bitnami.com` still serves, so pinned charts *sync* fine and the failure arrives later, at **image-pull time** — the first pod reschedule onto a node without the tag cached fails. Migrate deliberately, but don't assume the status quo is stable (full risk model: `references/airgap-gitops.md`). Valkey (Linux Foundation fork of Redis 7.2.4, BSD-licensed) is the sanctioned successor — major consumers (Harbor, GitLab) have adopted or officially support it. ## The one fact that shapes every plan: the RDB-version wall Valkey forked at Redis 7.2. Its replication and snapshot formats stayed at the fork point, then diverged on their own path: | Server | Writes RDB | Can load | |---|---|---| | Redis 7.0 | v10 | ≤ v10 | | Redis 7.2 | v11 | ≤ v11 | | Redis 7.4 / 8.x | **v12** | ≤ v12 | | Valkey 8.0 / 8.1 | v11 | ≤ v11 (v12+ rejected as foreign) | | Valkey 9.0 / 9.1 | **v80** (own numbering) | v11 and ...