v0.34.1

A route filter change now reconciles only the gateways that use it, and two extension server gauges that could hide a missed policy rebuild are removed.

Fixes

• A route filter change reconciles only the gateways that use it. Before, a change to one filter reconciled every gateway that uses any filter. A new setting, gateway.preciseEndpointSliceMapping, narrows endpoint changes the same way: an endpoint change reconciles only the gateways whose routes reach that workload, and a pod endpoint change that touches only readiness conditions reconciles none. It is off by default. (#747)
• Two traffic protection policy gauges are removed. nso_extension_tpp_cache_generation and nso_extension_tpp_applied_generation were both set inside the hook call, so an edge that missed a rebuild left them equal and hid the miss. Each policy target's Programmed condition reports a missed rebuild instead. (#775)

Documentation

• The delegation settings are documented. (#771)

Note

The extension server no longer exports nso_extension_tpp_cache_generation or nso_extension_tpp_applied_generation. A dashboard or rule that reads them shows no data.

Changelog

• e3702c0 Merge pull request #747 from datum-cloud/fix/endpoint-fanout
• a034bee Merge pull request #771 from datum-cloud/docs/delegation-settings
• e44fe63 Merge pull request #775 from datum-cloud/fix/remove-tpp-generation-gauges
• 71134cc fix: Map endpoint changes to affected gateways
• 7f68427 fix: Remove the TPP generation gauges, which cannot see a missed rebuild
• 1db9267 fix: reconcile only Gateways using a changed filter