Matt Moore

Ok, well once you have a PoC that can run the update test cleanly it'd be a useful tool to ensure that some of the other redness we are seeing...

Haven't triaged them yet because they are outside of ingress conformance, but I think they generally manifest as 503s, so tough to tell. Most are in tests are dealing with...

So with the scheme I just implemented in our net-contour controller, before we update our core `HTTPProxy` resources we first create an "endpoint probe" configuration that creates a virtual host...

Turning on the Envoy debug logging is a bit more useful. For every `503 NR`, we hit one of [these](https://github.com/envoyproxy/envoy/blob/c423b043d4b1662a23c5a5db9471b9ec29a10f26/source/common/router/router.cc#L464) log statements (which others may find obvious 😅). This let...

With a PoC of this, I now have two clean runs of the full Knative networking conformance (each running 5x) without any 503s. I also have two more runs of...

My PoC was working around this downstream in Knative's ingress implementation layered on top of Contour, which takes advantage of some readiness probing logic we have in Knative to ensure...

Gulp... 😅 You're on! cc @vaikas

@RichieEscarez that's super helpful, I will dig into that some more :)

I think that this is essentially what the tabs are hitting: ``` IMPORTANT: You cannot nest shortcodes. When the Hugo build runs on a file, any shortcodes within that file...

> where we see automatic staging builds in the website repo. FWIW I have this running against knative/docs PRs where it builds docs and website (HEAD) into a container image...