Repository navigation
v0.32.8
A WAF policy's Programmed on an edge now means the edge built it.
What's new
- Programmed only for what was built. The edge's extension server reports a WAF policy as programmed only after Envoy Gateway received a build that contains it, with one entry per target in that build, and removes an entry when its target leaves the policy or no longer exists. (#581)
- Builds no longer wait for status writes. The extension server writes these reports after it answers Envoy Gateway, not before. (#581)
- A missing permission is visible. An informer error, such as a missing right, is now logged instead of leaving the server waiting for its cache in silence. (#581)
Note
The extension server's role gains list and watch on Gateways and HTTPRoutes, and a new pod becomes ready only after its caches sync. Envoy Gateway must keep read-only access to TrafficProtectionPolicy on the edge. No schema changes; existing resources keep working without any conversion.