Nick Young

Thanks for the comment, @andrewzah. There's quite a bit to respond to, so I'll quote-and-reply. > Then it would be best to remove all custom Lua code support. If you...

I think that we can take the presented problems and add them as features, yes. @andrewzah has logged #3657 to cover the location header rewrite, and we already have #2965...

We _can_ have Lua support, and have it be not supported by the Contour team, but we would need to validate that sending a broken Lua to Envoy doesn't produce...

@pkit I'll be honest, I'm much more hopeful for WASM filters in this regard, as they are a bit less open-ended than Lua. You are correct that there's no way...

Yes, I agree that it would need an annotation, and would also need clear documentation about what would happen in various Ingress cases (like multiple vhosts).

With the addition of `ExtensionService`, including a Conditions block, we have the space available for Contour to set a `Ready` condition on an ExtensionService, this would indicate that the service...

I think what @stevesloka was referring to here was making it so that we can configure *Envoy* active health checking for gRPC backend services. You can do that for HTTP...

We removed the generated Informer types earlier because we weren't using them, and we didn't realise anyone else was. I don't see any issue with putting the generation back if...

Splitting the objects out to a new repo is doable but requires a bit of coordination.

Yes, I didn't look at the patch, my mistake. @shashwathi is your request just about bringing that patch upstream? I don't see any issues with that at all, although I...