v0.32.11

The operator now logs searchable JSON, each WAF policy copy carries its project's version, and a retrigger that rebuilt nothing is gone.

What's new

• Searchable, quieter logs. The operator logs JSON at info level by default and names objects instead of printing them whole; routine per-reconcile messages move to debug, and the zap flags still bring back debug console output. (#573)
• WAF policy copies carry the project's version. The hub copy of a TrafficProtectionPolicy, and each edge copy, carry networking.datumapis.com/upstream-generation: the project policy's generation. Nothing reads it in this release. (#593)
• One reconcile per WAF policy change. The extension server no longer writes a tpp-generation-* annotation on target Gateways, which made Envoy Gateway reconcile a second time without rebuilding anything. (#594)

Note

At start-up the replicator writes the new annotation on every WAF policy's hub copy once, so each edge reports its policies again and Envoy Gateway rebuilds once more. No schema changes; existing resources keep working without any conversion.

Changelog

• 7cb2185 Merge pull request #573 from datum-cloud/feat/logging-defaults
• 40c68db Merge pull request #593 from datum-cloud/feat/545-upstream-generation-stamp
• b3eefe7 Merge pull request #594 from datum-cloud/fix/546-remove-tpp-retrigger
• 601acbc feat: Stamp the upstream generation on a TPP's hub copy
• 8927d20 fix: Log JSON at info without sampling
• 6a3589a fix: Remove the TPP retrigger, which starts no rebuild