Closed as not planned
Closed as not planned
Description
What would you like to be added:
As a follow up to #2076, we should add test coverage to the TLSRoute test in that PR that makes an assertion on what a client sees when making a connection/request that match a Gateway/TLSRoute with no valid backends (due to invalid ReferenceGrant etc.)
Before we add a test, the language here likely needs a little more specificity (and we should make sure to write tests that match the new language), particularly what "reject" means:
gateway-api/apis/v1alpha2/tlsroute_types.go
Lines 104 to 108 in a5ede12
"Reject" could mean:
- Connection refused, so nothing listening on the relevant Gateway Listener port (probably not the right answer, since you could have multiple hostnames for the same port)
- Server sends TCP RST (what Envoy/Contour will do if there the Listener port is open but no proxying set up)
- Specific TLS error (seems less likely to be uniform across all implementors)
- other ideas welcome
Why this is needed:
Full coverage of TLSRoute API surface.
Related to #1579
We can probably do something similar for TCPRoute