HTTPRoute Timeout Tests can pass when implementations have timeouts setup

[dprotaso]

So I added this timeout test case to ensure implementations support disabling timeouts with 0s.

The times are pretty low (eg. 1s) delay. But for envoy implementations with default timeout values this passes. So now I'm wondering what's the best way to exercise that timeouts are disabled.

Looking for ideas on what to tweak here - one obvious thing to do is to increase the delay to something larger than most implementations default timeouts

gateway-api/conformance/tests/httproute-timeout-request.yaml

Lines 19 to 27 in 29e68bf

	- matches:
	- path:
	type: PathPrefix
	value: /disable-request-timeout
	backendRefs:
	- name: infra-backend-v1
	port: 8080
	timeouts:
	request: "0s"

gateway-api/conformance/tests/httproute-timeout-request.go

Lines 64 to 66 in 29e68bf

	Request: http.Request{Path: "/disable-request-timeout?delay=1s"},
	Response: http.Response{StatusCode: 200},
	Namespace: ns,

Note this applies to backend timeout tests as well

[robscott]

So now I'm wondering what's the best way to exercise that timeouts are disabled.

I don't think you can. We had a similar discussion in the earlier days of the timeout GEP, it's ~impossible to write a test that confirms that timeouts are disabled. You could theoretically write a test that ran for a week, but how many dataplanes really support that? The general idea is that "disabling" a timeout in this case is really just setting the value to the max an implementation supports. In many cases this will be tied to how often the underlying infrastructure is updated or replaced.

[dprotaso]

Yeah I agree with your points.

Maybe then better visibility is what's needed - #3012