John Esmet

This issue https://github.com/envoyproxy/envoy/issues/4124 and the associated PR https://github.com/envoyproxy/envoy/pull/4199 introduced this behavior, I think.

@yanniszark I agree. It sounds like we want to add configuration to set the definition of an error for the external authorization server. Similar to https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/router_filter#x-envoy-retry-on but of course we...

By definition of error, I mean the case where a call to the authorization service is considered "failed" as opposed to "completed, but with an error". Today, the ext_authz filter...

> @esmet got it! IMO the current behavior of > > > Today, the ext_authz filter considers "completed, but with a 5xx error" to be "failed" > > is a...

> > do you think mimicking the retry-on configuration is the right path forward? > > I think so. Yes, it actually controlled by an array of pre-defined strings. Probably...

Let's move this to "no stale bot"

I believe Ambassador has an option to rewrite the host header value, but not generate the service name dynamically. I think the way I've seen this done in the past...

I don't think host_rewrite supports a regex right now, so I see how that would be a gap in implementing what you need right.

Looking more deeply, I don't think Envoy supports rewriting the Host header based on the incoming host header. It does, however, support host rewriting based on the incoming path. I...

Would the host regex rewrite be enough to cover this use case? I think that's a reasonable feature request. Something like ``` host: '(.*).k8s.mycompany.local' host_regex: true host_rewrite: \1.k8s2.mycompany.local host_rewrite_regex: true...