Skip to content

v0.32.9

Choose a tag to compare

View all tags
@vvoytovych vvoytovych released this 09 Oct 15:58
v0.32.9
9d61d69
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Gateways now reconcile when something they depend on changes, not on a timer or on unrelated changes.

What's new

  • Only the Gateways a slice serves. A change to a VPC pod EndpointSlice now reconciles only the Gateways whose routes name that slice, instead of every Gateway in the project. (#586)
  • No 5-second polling. A Gateway that waits for its downstream copy to be accepted and programmed, or to get its IP addresses, is now reconciled when that copy changes, instead of every 5 seconds. (#587)
  • A released hostname wakes its waiters. A Gateway refused because another Gateway holds its hostname is reconciled as soon as a hostname claim is released. (#587)
  • Downstream annotations are kept. Writing a downstream Gateway no longer replaces all its annotations, so the certificate reissuance count kept there survives each reconcile. (#587)
  • NOTICE lists the MCP dependencies. The third-party license file now covers the MCP Go SDK and the libraries that came with it. (#590)

Note

A downstream Gateway that waits for a hostname claim carries the annotation networking.datumapis.com/awaiting-hostname-claim. No schema changes; existing resources keep working without any conversion.

Changelog

  • 62745d0 Merge pull request #586 from datum-cloud/fix/vpc-pod-slice-wakes-only-its-gateways
  • d398486 Merge pull request #587 from datum-cloud/fix/gateway-waits-on-events
  • 9d61d69 Merge pull request #590 from datum-cloud/chore/refresh-notice-mcp
  • b4c540d fix: Reconcile a waiting Gateway when what it waits for changes
  • 0029b1d fix: Reconcile only Gateways whose routes name a changed VPC pod slice
Assets 8
Loading