hey, so from what I understand, you don't need to apply config version by version. when you specify a target version, the operator walks through the update graph on its own and handles all the intermediate steps, stopping once it hits your target version. that said, a few things worth double checking before you go ahead: first, make sure v1.53.0 actually exists in the update graph bundled with operator v1.25.0, since the graph is shipped inside the operator itself. you can verify after applying the operator with: kubectl get configmap -n spicedb-operator-system -o yaml | grep v1.53 second, since you're on Postgres, there's a phased migration at v1.30.0 you should be aware of. the operator handles it automatically through an intermediate node, but just good to know you might see it pause there briefly. third, just to sanity check, the version and channel should be under spec, not status. status is read-only and written by the operator. so your config should look like: spec: channel: stable version: v1.53.0 config: datastoreEngine: postgres and you can watch the rollout live with: kubectl get spicedbcluster -o yaml -w and check status.version to see where it currently is.