Jacob Bohanon

https://github.com/solo-io/gloo/pull/8487

I'd guess `healthy_panic_threshold: {}` might have something to do with this in their env. In your sample steps what happens if you turn off UDS and manually define v1 service...

> In this bug we get a no healthy upstream error rather than upstream connect error or disconnect/reset before headers. reset reason: connection termination . So it detects the upstream...

This is a valuable learning that we should capture somewhere. User-facing docs may be a good place to clarify that this translates to routing and not cluster config. On Tue,...

Analyzing build logs it looks like this flake first started appearing on 3/25

The team consensus at sprint planning today is to punt this discussion down to road to when GGv2 team is implementing analogous kubernetes end-to-end tests. @sam-heilbron raising this issue to...

@nfuden @sam-heilbron I am unclear what this issue is tracking at this point. Can this be closed?

In October, we presented a resolution to this issue whereby we injected a `Connection: Close` header to requests to the upstream in hopes that this would help resolve the intermittent...

The [static analysis](https://app.codacy.com/gh/pantor/inja/pullRequest?prid=12008471) says the field `ParserConfig::notation` is never used, but this is used in the construction of the `DataNode` [here](https://github.com/solo-io/inja/blob/5a18986825fc7e5d2916ff345c4369e4b6ea7122/include/inja/parser.hpp#L240-L241)

Also (for posterity) https://github.com/solo-io/gloo/pull/9005#pullrequestreview-1789516162