Sunjay Bhatia

> > > Looks like `HTTPRouteHTTPSListener` is failing, it expects a 404 for request to a HTTPS listener with an unknown hostname > > > Seems like we should either...

upgrade test probably failing since we started reconciling v1alpha3 backendtlspolicy and that has not been applied to the cluster as part of the upgrade

Listener isolation test failing, needs this fix: https://github.com/projectcontour/contour/pull/6162

disabled backendtlspolicy feature in provisioner upgrade test since the upgrade from v1.0.0 to v1.1.0 of gw api removes the old api version and adds v1alpha3 of the resource i tried...

> disabled backendtlspolicy feature in provisioner upgrade test since the upgrade from v1.0.0 to v1.1.0 of gw api removes the old api version and adds v1alpha3 of the resource >...

> Is there any way to apply per IP rate limit? Seems like local rate limits do not care about IP and only thing is they care is how many...

The latest Windows image size has been reduced (see https://hub.docker.com/r/envoyproxy/envoy-build-windows2019/tags?page=1&ordering=last_updated) by a GB when compressed (4.73GB - 3.79GB) and uncompressed (10.5GB - 9.64GB) But yeah, the two things we're fighting...

This PR also reduces the image size a bit once we added the Windows 10 SDK back correctly: https://github.com/envoyproxy/envoy-build-tools/pull/95

The hard part about moving images to ones based on a semi annual release channel is that you need the host OS to match, not sure if its feasible to...

Maybe we can do all CI builds on a smaller image but publish 2019 images as well for the public (the build image and envoy release image)