limitador cluster envoy filter leverages DAG #528
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Limitador cluster envoy filter controller reading from DAG Gateway API topology and RateLimitPolicies
Kuadrant rate limiting controllers no longer depends on back references annotation:
kuadrant.io/ratelimitpolicies
. Instead, controllers rely on the DAG Gateway API topopology to read cluster state. Kuadrant envoy filter controller is also based on this approach.Fix reconciliation event blind spots due to race conditions or timing issues. The reconciled resource reflects latest updates from the cluster (Gateways, Routes and policies).
Built on top of #527, so that must be merged first (not a hard requirement, though)