Our free plan has no disk, so Valkey runs with appendonly no and save "" , so when the pod restarts, the customer's data is gone.
That one fact shaped most of our Kubernetes operator. If rotating a password restarts the pod, a routine security task wipes someone's cache. So, as expected, we split configuration into two classes: changes that need a restart, and changes that must never cause one.
This post walks through how the operator works and why it's built this way, including the parts that aren't finished.
Disclosure: this is the operator behind KVNest , the managed Redis and Valkey service we run. Versions and numbers are as of November 2026.
TL;DR
One cluster-scoped custom resource becomes up to nine child objects, nearly all in a dedicated namespace.
Children are created in dependency order, so a pod never exists without its quota and NetworkPolicy.
Server settings are hashed into a pod annotation and trigger a rollout.…