Duncan Doyle

Closing. Matches rule was incorrectly specified. Route should look as such. Notice that we removed the dash on the `headers` field. With the dash, we were defining 2 matching rules...

So, if we look at the application policy for RL, we currently have "alwaysApply=true" and "alwaysApply=false". Now, say we have RL1 and RL2 in one config (pseudo code): ``` rateLimit:...

@idogoren: It's targeted for 1.17. Top of the list in our prio queue for engineering to pick it up.

Treating this as a separate issue. Seems related to #7976, but that ticket seems to focus more on invalid routes in delegated routetables, where this ticket has clear requirements wrt...

Additional context: ``` In my local minikube with gloo 1.16 I could validate that the following situations do not put Gloo in this unstable state: - VirtualService referencing missing Upstream...

Question on this: what is the requirement to have multiple Redis pods? Is that for HA/failover, read performance or for horizontal storage scaling. In the first 2 cases, Redis clustered...

@sam-heilbron Feedback from another customer is that setting this to the gateway name also fits their use-case and requirements. So I agree with @anessi, let's set this to the gateway...

@nfuden: Since this "works as expected", can we close this one as "Not a bug - won't fix"?

@nfuden: I did find the documentation in Envoy on discovered upstreams: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/service_discovery I know we have documentation on static upstreams in our GE docs: https://docs.solo.io/gloo-edge/latest/guides/traffic_management/destination_types/static_upstream/ ... but I couldn't find...

Can't reproduce on 1.15.14 when using `strict_dns` (which is created when you use a hostname in the static `Upstream`). Reproducer project here: https://github.com/DuncanDoyle/ge-gloo-6331