@rahulanand16nov could you propose a new flow for the demo here based on the feedback received on the first one
Currently the RLP implementation supports a form of override functionality when a RLP is applied to a gateway.
Demo 1 overrides
Using service registry.
Create a RateLimitPolicy that targets the gateway and a global rate limit for all hosts
Show that this limit is applied to the service registry (with no RateLimitPolicy in their namespace)
Create a RateLimitPolicy in the service registry namespace that targets the HTTPRoute of service and sets a different global rate limit rule plus a new limit for the upload path
Show that the new limit takes effect
Show that the RLP in the developer namespace shows the "Effective" policy based on what was applied at the gateway level
[ ] Share demo and Design with Istio upstream and Gateway API
@rahulanand16nov could you propose a new flow for the demo here based on the feedback received on the first one
Currently the RLP implementation supports a form of override functionality when a RLP is applied to a gateway.
Demo 1 overrides
Using service registry.
Create a RateLimitPolicy that targets the gateway and a global rate limit for all hosts
Show that this limit is applied to the service registry (with no RateLimitPolicy in their namespace)
Create a RateLimitPolicy in the service registry namespace that targets the HTTPRoute of service and sets a different global rate limit rule plus a new limit for the upload path
Show that the new limit takes effect
Show that the RLP in the developer namespace shows the "Effective" policy based on what was applied at the gateway level
[ ] Share demo and Design with Istio upstream and Gateway API