v2.2.0

Restate Operator v2.2.0

✨ New Features

• Knative Serving deployment mode — RestateDeployment now supports Knative Serving as an alternative to traditional ReplicaSets. This enables:

  • Scale-to-zero: Services automatically scale down when idle, saving resources
  • Automatic scaling: Replicas scale based on concurrent request load
  • In-place updates: Update service implementation without changing Restate deployment identity
  • Tag-based identity: Control versioning behavior with the tag field — same tag means in-place update, changed tag means versioned update, no tag means auto-versioning

  See the Knative Serving Mode documentation for details. (#64)

🐛 Bug Fixes

• Fix DNS network policy for NodeLocal DNSCache — The operator now creates DNS egress policies that work with both traditional kube-dns and NodeLocal DNSCache (169.254.20.10). This fixes DNS resolution issues on GKE Autopilot and other Kubernetes environments using node-local DNS caching. (#88)

⚙️ Configuration Changes

• Default partitions increased to 24 — The default number of partitions is now 24 (previously lower), providing better parallelism for most workloads. (#84)

📝 Documentation

• Added dedicated Knative Serving mode section to README with examples and tag-based versioning guide
• Added troubleshooting section for DNS resolution issues
• Updated RocksDB memory documentation (#82)

---

⚠️ Upgrading Notes

CRD Update Required: Helm does not automatically upgrade CRDs. After upgrading the operator, you must manually apply the updated CRDs:

kubectl apply --server-side -f https://github.com/restatedev/restate-operator/releases/download/v2.2.0/restateclusters.yaml
kubectl apply --server-side -f https://github.com/restatedev/restate-operator/releases/download/v2.2.0/restatedeployments.yaml
kubectl apply --server-side -f https://github.com/restatedev/restate-operator/releases/download/v2.2.0/restatecloudenvironments.yaml

Note: The restatedeployments CRD update is especially important for this release as it includes the new Knative Serving deployment mode fields.

Then upgrade the operator via Helm:

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

---

New Contributors

• @AhmedSoliman made their first contribution in #82

Full Changelog: v2.1.0...v2.2.0

v2.2.0-alpha1

What's Changed

• Add Knative Serving deployment mode with scale-to-zero and in-place updates by @EronWright in #64

Full Changelog: v2.1.0...v2.2.0-alpha1

v2.1.0

✨ New Features

• Operator-driven cluster provisioning - Added support for automatic cluster provisioning via the new spec.cluster.autoProvision field. When enabled, the operator will automatically provision the Restate cluster by calling the gRPC ProvisionCluster API after pods are running. This is particularly useful for multi-node clusters where manual provisioning was previously required. The provisioning status is tracked in status.provisioned to prevent repeated provisioning attempts. (#55)

  ⚠️ Important: When using cluster.autoProvision: true, you must set auto-provision = false in your Restate config to avoid split brain situations.

  🎯 cluster.autoProvision: true is the recommended approach for provisioning Restate clusters.

🔧 Improvements

• Simplified example configurations by removing default values that are no longer needed (replicated loglet and replicated metadata server are now defaults)

🏗️ CRD Changes

• Added spec.cluster.autoProvision field to enable operator-managed cluster provisioning
• Added status.provisioned field to track provisioning state

⬆️ Upgrading

CRD Update Required: Helm does not automatically upgrade CRDs. After upgrading the operator, you must manually apply the new CRDs:

kubectl apply -f https://github.com/restatedev/restate-operator/releases/download/v2.1.0/restateclusters.yaml
kubectl apply -f https://github.com/restatedev/restate-operator/releases/download/v2.1.0/restatedeployments.yaml
kubectl apply -f https://github.com/restatedev/restate-operator/releases/download/v2.1.0/restatecloudenvironments.yaml

Full Changelog: v2.0.0...v2.1.0

v2.0.0

What's Changed

• Update default tunnel client version by @jackkleeman in #81

Full Changelog: v1.9.2...v2.0.0

v1.9.2

What's Changed

• Avoid reconcile loop in netpol peer list by @jackkleeman in #73

Full Changelog: v1.9.1...v1.9.2

v1.9.1

What's Changed

• Ignore completed invs when determining active invocations by @jackkleeman in #71

Full Changelog: v1.9.0...v1.9.1

v1.9.0

What's Changed

• [Security] Update assorted dependencies by @pcholakov in #69
• Support existing namespaces by @jackkleeman in #70

Full Changelog: v1.8.4...v1.9.0

v1.8.4

What's Changed

• Add priorityClassName to restatecluster by @pcholakov in #63
• Release v1.8.4 by @pcholakov in #66

Full Changelog: v1.8.3...v1.8.4

Release v1.8.3

What's Changed

• Add service path parameter by @krisztiansala in #56
• feat: Add topology spread constraints support to RestateCluster by @EronWright in #60
• Delete jobs on immutable conflict by @jackkleeman in #61
• Release v1.8.3 by @pcholakov in #62

New Contributors

• @EronWright made their first contribution in #60

Full Changelog: v1.8.2...v1.8.3

v1.8.2

What's Changed

• Allow cleaning up old replicasets while the new one is not ready by @jackkleeman in #59

Full Changelog: v1.8.1...v1.8.2