From 6ca32ecf4a3a598f5de6ffd365cebb52337dfbea Mon Sep 17 00:00:00 2001 From: Sara Thomas Date: Tue, 1 Mar 2022 11:19:13 -0500 Subject: [PATCH] GH##40734: adding passthrough route as tlsinspectdelay option --- modules/nw-ingress-controller-configuration-parameters.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/nw-ingress-controller-configuration-parameters.adoc b/modules/nw-ingress-controller-configuration-parameters.adoc index 870f87489a..61289e76dd 100644 --- a/modules/nw-ingress-controller-configuration-parameters.adoc +++ b/modules/nw-ingress-controller-configuration-parameters.adoc @@ -191,7 +191,7 @@ supports up to `64` threads. If this field is empty, the Ingress Controller uses * `clientFinTimeout` specifies how long a connection is held open while waiting for the client response to the server closing the connection. If unset, the default timeout is `1s`. -* `tlsInspectDelay` specifies how long the router can hold data to find a matching route. Setting this value too short can cause the router to fall back to the default certificate for edge-terminated or reencrypted routes, even when using a better matched certificate. If unset, the default inspect delay is `5s`. +* `tlsInspectDelay` specifies how long the router can hold data to find a matching route. Setting this value too short can cause the router to fall back to the default certificate for edge-terminated, reencrypted, or passthrough routes, even when using a better matched certificate. If unset, the default inspect delay is `5s`. * `tunnelTimeout` specifies how long a tunnel connection, including websockets, remains open while the tunnel is idle. If unset, the default timeout is `1h`.