v0.7.1

v0.7.1 restores support for Kubernetes 1.31.

Fixes

CRDs apply on Kubernetes 1.31 again (#473)

In v0.7.0 the serverName validation rule used the CEL format library, which a 1.31 API server does not have for CRD rules, so both CRDs failed to apply there. The rule now uses self.matches() with the same DNS-1123 subdomain regex. It accepts and rejects the same names, with the same error message. The minimum supported Kubernetes version is back to 1.31.

Upgrade notes

From v0.7.0

Only the CRDs change. Apply them:

kubectl apply --server-side --force-conflicts -f https://raw.githubusercontent.com/valkey-io/valkey-operator/v0.7.1/config/crd/bases/valkey.io_valkeyclusters.yaml
kubectl apply --server-side --force-conflicts -f https://raw.githubusercontent.com/valkey-io/valkey-operator/v0.7.1/config/crd/bases/valkey.io_valkeynodes.yaml

Then update the operator image. There is no operator code change, so Valkey pods are not rolled.

From v0.6.0

Follow the v0.7.0 upgrade notes, using the v0.7.1 CRDs. The Kubernetes 1.32 requirement no longer applies: 1.31 is supported.

What's Changed

• fix: validate serverName without the CEL format library so the CRDs apply on Kubernetes 1.31 by @jdheyburn in #473

Full Changelog: v0.7.0...v0.7.1