Skip to content

v2.6.1

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Jun 17:07
v2.6.1
ecaf8c7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Restate Operator v2.6.1 Release Notes

Highlights

  • Fix: in-process Restate Cloud tunnels now accept BYOC regions - RestateCloudEnvironment.spec.region may now contain multiple DNS labels, such as inl4edhpbxasp9yuz1n0yvvkme.byoc, when used with RestateDeployment in tunnelMode: in-process.

Bug Fixes

In-process tunnel mode rejected multi-label BYOC regions

The tunnelMode: in-process validation for RestateCloudEnvironment regions
only allowed a single lowercase DNS label ([a-z0-9-]). This rejected BYOC
Cloud environments whose regions are represented as multiple labels, for
example:

spec:
  region: inl4edhpbxasp9yuz1n0yvvkme.byoc

Those regions are valid for the tunnel hostname
tunnel.<region>.restate.cloud, and the centralized tunnel path already
accepted them. The operator now allows dots in the region while still rejecting
invalid dotted forms with empty labels, such as .us, us., and us..eu.

Impact on Users:

  • BYOC Restate Cloud environments using RestateDeployment with
    tunnelMode: in-process can now reconcile and register successfully.
  • Standard single-label regions such as us and eu are unchanged.
  • Malformed region values are still rejected during reconciliation with an
    InvalidRestateConfig error.

Migration Guidance:
No configuration changes are required. Upgrade the operator if you use
in-process tunnels against BYOC Restate Cloud environments.

Related: PR #147

Upgrading

No CRD changes in this release. Upgrade the operator via Helm:

helm upgrade restate-operator restatedev/restate-operator --version 2.6.1
Assets 5
Loading