v2.8.1

Restate Operator v2.8.1 Release Notes

See the v2.7.0 release notes for changes prior to this release. (v2.8.0 was an unpublished, broken release and is superseded by v2.8.1.)

CRD installation

The chart's CRDs (RestateCluster, RestateDeployment, RestateCloudEnvironment) now ship via an optional restate-operator-crds subchart that places them in Helm's native crds/ directory. Installation is gated by the installCrds value (default true).

• Fresh installs get all three CRDs by default.

• Set installCrds: false to manage the CRDs out-of-band (BYOC / GitOps):

  installCrds: false

Upgrading

Upgrading from <= 2.7 is uneventful. Existing CRDs are left untouched — there is no ownership adoption, no invalid ownership metadata error, and no --take-ownership step. helm uninstall never deletes the CRDs or your custom resources.

helm upgrade restate-operator restatedev/restate-operator --version 2.8.1

Note on CRD schema updates

Native crds/ are install-only under helm upgrade — this is Helm's deliberately conservative CRD lifecycle, and it means chart upgrades will not apply CRD schema changes to an existing install. To update CRD schemas, apply the new CRDs explicitly:

kubectl apply -f crd/restateclusters.yaml -f crd/restatedeployments.yaml -f crd/restatecloudenvironments.yaml

or let a GitOps tool re-apply them on sync (e.g. ArgoCD). The CRDs are also published as GitHub release artifacts (crd/restateclusters.yaml, crd/restatedeployments.yaml, crd/restatecloudenvironments.yaml).