fix: align backend timeout documentation, and Traefik timeouts sequen…

…ce diagram
kubernetes-sigs · Feb 18, 2025 · 65d5bf4 · 65d5bf4
1 parent d936258
commit 65d5bf4
Show file tree

Hide file tree

Showing 5 changed files with 9 additions and 9 deletions.
diff --git a/apis/openapi/zz_generated.openapi.go b/apis/openapi/zz_generated.openapi.go
diff --git a/apis/v1/httproute_types.go b/apis/v1/httproute_types.go
@@ -347,7 +347,7 @@ type HTTPRouteTimeouts struct {
 
 	// BackendRequest specifies a timeout for an individual request from the gateway
 	// to a backend. This covers the time from when the request first starts being
-	// sent from the gateway to when the full response has been received from the backend.
+	// sent from the gateway to when the response headers have been received from the backend.
 	//
 	// Setting a timeout to the zero duration (e.g. "0s") SHOULD disable the timeout
 	// completely. Implementations that cannot completely disable the timeout MUST

diff --git a/config/crd/experimental/gateway.networking.k8s.io_httproutes.yaml b/config/crd/experimental/gateway.networking.k8s.io_httproutes.yaml
diff --git a/config/crd/standard/gateway.networking.k8s.io_httproutes.yaml b/config/crd/standard/gateway.networking.k8s.io_httproutes.yaml
diff --git a/geps/gep-1742/index.md b/geps/gep-1742/index.md
@@ -270,15 +270,15 @@ sequenceDiagram
     Note right of P: respondingTimeouts<br/>readTimeout
     C->>P: Finishes request
     deactivate P
-    P->>U: Connection Started
     activate U
+    P->>U: Connection Started
     Note right of U: forwardingTimeouts<br/>dialTimeout
     deactivate U
+    activate U
     P->>U: Starts sending Request
     P->>U: Finishes request
     P->>U: Finishes Headers
     U->>P: Starts Response
-    activate U
     note right of U: forwardingTimeouts<br/>responseHeaderTimeout
     U->>P: Finishes Headers
     deactivate U
@@ -418,7 +418,7 @@ type HTTPRouteTimeouts struct {
 
 	// BackendRequest specifies a timeout for an individual request from the gateway
 	// to a backend. This covers the time from when the request first starts being
-	// sent from the gateway to when the full response has been received from the backend.
+	// sent from the gateway to when the response headers have been received from the backend.
 	//
 	// An entire client HTTP transaction with a gateway, covered by the Request timeout,
 	// may result in more than one call from the gateway to the destination backend,