Skip to content

Commit 30638c4

Browse files
authored
Merge pull request #124 from restatedev/chore/bump-patch
chore: bump for patch release + notes
2 parents 10b017e + 0a67805 commit 30638c4

4 files changed

Lines changed: 41 additions & 3 deletions

File tree

Cargo.lock

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "restate-operator"
3-
version = "2.5.0"
3+
version = "2.5.1"
44
authors = ["restate.dev"]
55
edition = "2024"
66
rust-version = "1.92"

charts/restate-operator-helm/Chart.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@ apiVersion: v2
22
name: restate-operator-helm
33
description: An operator for Restate clusters
44
type: application
5-
version: "2.5.0"
5+
version: "2.5.1"

release-notes/v2.5.1.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# Restate Operator v2.5.1 Release Notes
2+
3+
## Highlights
4+
5+
- **Fix: Knative deployments now work with Restate Cloud** — The Knative reconciler was passing raw in-cluster Route URLs to the Restate admin API, which Restate Cloud cannot reach. Service URLs are now routed through the cloud tunnel, matching the existing ReplicaSet behavior.
6+
7+
## Bug Fixes
8+
9+
### Knative service URLs not tunneled for Restate Cloud
10+
11+
When using RestateDeployment in Knative mode with a Restate Cloud endpoint
12+
(`spec.restate.register.cloud`), the operator passed the in-cluster Knative
13+
Route URL directly to `register_service_with_restate`. Restate Cloud cannot
14+
reach in-cluster URLs, so registration failed and the operator looped
15+
indefinitely.
16+
17+
The fix extracts a `maybe_tunnel_url()` method from `RestateAdminEndpoint` and
18+
calls it in the Knative reconciler after resolving the Route URL, matching how
19+
the ReplicaSet reconciler already handled this case.
20+
21+
**Impact on Users:**
22+
- **Knative + Restate Cloud deployments**: This was broken; it now works.
23+
- **Knative + non-Cloud deployments**: No change; `maybe_tunnel_url` is a no-op
24+
when `cloud` is not set.
25+
- **ReplicaSet deployments**: No change. The internal refactoring of
26+
`service_url_for_deployment()` is equivalent to the previous behavior.
27+
28+
*Related: Issue [#120](https://github.com/restatedev/restate-operator/issues/120), PR [#122](https://github.com/restatedev/restate-operator/pull/122)*
29+
30+
---
31+
32+
## Upgrading
33+
34+
No CRD changes in this release. Upgrade the operator via Helm:
35+
36+
```bash
37+
helm upgrade restate-operator restatedev/restate-operator --version 2.5.1
38+
```

0 commit comments

Comments
 (0)