Repository: openshift/openshift-docs
Pull request #88871: [SRVKS-1289] Timeout seconds for revisions - follow up
Author: login: ochromy
Labels: name: peer-review-done
description: Signifies that the peer review team has reviewed this PR
name: size/L
description: Denotes a PR that changes 100-499 lines, ignoring generated files.
name: serverless
description: Label for all Serverless PRs
name: merge-review-in-progress
description: Signifies that the merge review team is reviewing this PR
Created: 2025-02-19T12:21:59Z | Merged: 2025-05-27T14:08:47Z

Version(s):
serverless-docs-1.34+

Issue:
https://issues.redhat.com/browse/SRVKS-1289

Link to docs preview:
- https://88871--ocpdocs-pr.netlify.app/openshift-serverless/latest/knative-serving/config-applications/configuring-revision-timeouts.html

QE review:
- [x] QE has approved this change.

Additional information:
_Merge AFTER [SRVKS-1306](https://github.com/openshift/openshift-docs/pull/89935)._



Diff:
diff --git a/knative-serving/config-applications/configuring-revision-timeouts.adoc b/knative-serving/config-applications/configuring-revision-timeouts.adoc
index 3f2de8405d9b..91d510a94d66 100644
--- a/knative-serving/config-applications/configuring-revision-timeouts.adoc
+++ b/knative-serving/config-applications/configuring-revision-timeouts.adoc
@@ -14,6 +14,12 @@ include::modules/configuring-revision-timeout.adoc[leveloffset=+1]
 //Configuring maximum revision timeout
 include::modules/configuring-maximum-revision-timeout.adoc[leveloffset=+1]
 
+//Configuring revision response to start timeout
+include::modules/serverless-configuring-response-start-timeout.adoc[leveloffset=+1]
+
+//Configuring idle revision timeout
+include::modules/serverless-configuring-revision-idle-timeout.adoc[leveloffset=+1]
+
 //Long-running requests
 include::modules/serverless-long-running-requests.adoc[leveloffset=+1]
 
diff --git a/modules/configuring-maximum-revision-timeout.adoc b/modules/configuring-maximum-revision-timeout.adoc
index cd2f05dde643..2cf90671cd53 100644
--- a/modules/configuring-maximum-revision-timeout.adoc
+++ b/modules/configuring-maximum-revision-timeout.adoc
@@ -1,26 +1,25 @@
 // Module included in the following assemblies:
 //
 // * knative-serving/config-applications/configuring-revision-timeouts.adoc
-:_content-type: PROCEDURE
+
+:_mod-docs-content-type: PROCEDURE
 [id="configuring-maximum-revision-timeout_{context}"]
 = Configuring maximum revision timeout
 
-By seting the maximum revision timeout, you can ensure that no revision can exceed a specific limit.
+By seting the maximum revision timeout, you can ensure that no revision can exceed a specific limit. The value of your maximum revision timeout must not exceed the `terminationGracePeriodSeconds` value of the activator to prevent in-flight requests being disrupted.
 
 .Prerequisites
 
 * You have installed the {ServerlessOperatorName} and Knative Serving.
-* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+* You have the required permissions for your cluster:
+** Cluster administrator permissions on {ocp-product-title}
+** Cluster administrator or dedicated administrator permissions on {rosa-product-title}
+** Cluster administrator or dedicated administrator permissions on {dedicated-product-title}
 
 .Procedure
 
 * To configure the maximum revision timeout, set the `max-revision-timeout-seconds` field in the `KnativeServing` custom resource (CR):
 +
-[NOTE]
-----
-If this value is increased, the activator `terminationGracePeriodSeconds` should also be increased to prevent in-flight requests being disrupted.
-----
-+
 [source,yaml]
 ----
 apiVersion: operator.knative.dev/v1beta1
@@ -33,3 +32,11 @@ spec:
     defaults:
       max-revision-timeout-seconds: "600"
 ----
+
++
+[NOTE]
+====
+To set the maximum revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout. 
+
+For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long-running requests".
+====
diff --git a/modules/configuring-revision-timeout.adoc b/modules/configuring-revision-timeout.adoc
index d501c846b5ce..be32d0b671b7 100644
--- a/modules/configuring-revision-timeout.adoc
+++ b/modules/configuring-revision-timeout.adoc
@@ -1,7 +1,8 @@
 // Module included in the following assemblies:
 //
 // * knative-serving/config-applications/configuring-revision-timeouts.adoc
-:_content-type: PROCEDURE
+
+:_mod-docs-content-type: PROCEDURE
 [id="configuring-revision-timeout_{context}"]
 = Configuring revision timeout
 
@@ -10,7 +11,10 @@ You can configure the default number of seconds for the revision timeout based o
 .Prerequisites
 
 * You have installed the {ServerlessOperatorName} and Knative Serving.
-* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+* You have the required permissions for your cluster:
+** Cluster administrator permissions on {ocp-product-title}
+** Cluster administrator or dedicated administrator permissions on {rosa-product-title}
+** Cluster administrator or dedicated administrator permissions on {dedicated-product-title}
 
 .Procedure
 
@@ -45,3 +49,11 @@ spec:
       containers:
       - image: ghcr.io/knative/helloworld-go:latest
 ----
+
++
+[NOTE]
+====
+To set the revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout and the maximum revision timeout. 
+
+For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long-running requests".
+====
diff --git a/modules/serverless-configuring-response-start-timeout.adoc b/modules/serverless-configuring-response-start-timeout.adoc
new file mode 100644
index 000000000000..3af66db86cdf
--- /dev/null
+++ b/modules/serverless-configuring-response-start-timeout.adoc
@@ -0,0 +1,63 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving waits for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default duration is 300 seconds (5 minutes).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have the required permissions for your cluster:
+** Cluster administrator permissions on {ocp-product-title}
+** Cluster administrator or dedicated administrator permissions on {rosa-product-title}
+** Cluster administrator or dedicated administrator permissions on {dedicated-product-title}
+
+.Procedure
+
+* Choose the appropriate method to configure the revision response start timeout:
+** To configure the timeout globally, set the `revision-response-start-timeout-seconds` field in your `KnativeServing` custom resource (CR). If your required response start timeout exceeds the revision timeout, also adjust the `revision-timeout-seconds` field accordingly:
++
+.Example of revision response start timeout globally set to 300 seconds (5 minutes)
+[source,yaml]
+----
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+  namespace: knative-serving
+spec:
+  config:
+    defaults:
+      revision-timeout-seconds: "600"
+      revision-response-start-timeout-seconds: "300"
+----
++
+** To configure the timeout per revision, set the `responseStartTimeoutSeconds` field in your service definition. If your required response start timeout exceeds the revision timeout, also adjust the `timeoutSeconds` field accordingly:
++
+.Example of a service definition with revision response start timeout set to 300 seconds (5 minutes)
+[source,yaml]
+----
+apiVersion: serving.knative.dev/v1
+kind: Service
+metadata:
+  namespace: my-ns
+spec:
+  template:
+    spec:
+      timeoutSeconds: 600
+      responseStartTimeoutSeconds: 300
+      containers:
+# ...
+----
+
++
+[NOTE]
+====
+To set the revision response start timeout and the revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout and the maximum revision timeout. 
+
+For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long-running requests".
+====
diff --git a/modules/serverless-configuring-revision-idle-timeout.adoc b/modules/serverless-configuring-revision-idle-timeout.adoc
new file mode 100644
index 000000000000..6795c09fffd9
--- /dev/null
+++ b/modules/serverless-configuring-revision-idle-timeout.adoc
@@ -0,0 +1,53 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-revision-idle-timeout_{context}"]
+= Configuring revision idle timeout
+
+By setting the revision idle timeout, you can specify the maximum duration in seconds a request is allowed to stay open without receiving data from the application. The default duration is `0` (infinite).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have the required permissions for your cluster:
+** Cluster administrator permissions on {ocp-product-title}
+** Cluster administrator or dedicated administrator permissions on {rosa-product-title}
+** Cluster administrator or dedicated administrator permissions on {dedicated-product-title}
+
+.Procedure
+
+* Choose the appropriate method to configure the revision idle timeout:
+** To configure the timeout globally, set the `revision-idle-timeout-seconds` field in your `KnativeServing` custom resource (CR):
++
+.Example of revision idle timeout globally set to 300 seconds (5 minutes)
+[source,yaml]
+----
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+  namespace: knative-serving
+spec:
+  config:
+    defaults:
+      revision-idle-timeout-seconds: "300"
+----
++
+** To configure the timeout per revision, set the `idleTimeoutSeconds` field in your service definition:
++
+.Example of a service definition with revision idle timeout set to 300 seconds (5 minutes)
+[source,yaml]
+----
+apiVersion: serving.knative.dev/v1
+kind: Service
+metadata:
+  namespace: my-ns
+spec:
+  template:
+    spec:
+      idleTimeoutSeconds: 300
+      containers:
+# ...
+----
diff --git a/modules/serverless-long-running-requests.adoc b/modules/serverless-long-running-requests.adoc
index 677e5f4a80a1..30bca59eb3aa 100644
--- a/modules/serverless-long-running-requests.adoc
+++ b/modules/serverless-long-running-requests.adoc
@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="serverless-long-running-requests_{context}"]
-= Long running requests
+= Long-running requests
 
 To ensure that requests exceeding the default 600 second timeout set by Knative are not prematurely terminated, you need to adjust the timeouts in the following components:
 


Reviews:
user: login: maschmid
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-25T16:54:09Z
user: login: ochromy
state: COMMENTED
author_association: NONE
submitted_at: 2025-03-27T10:06:20Z
user: login: lahinson
body: Really nice work here! Just a couple of minor suggestions for your consideration.
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-27T14:29:10Z
user: login: maschmid
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-31T10:30:45Z
user: login: xenolinux
body: Left a few comments. IIRC, there was a PR with the similar content, I remember giving similar feedback. Can you please go back to that PR and apply similar changes in this PR?

overall lgtm
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-08T08:04:54Z
user: login: kcarmichael08
body: This looks good, just had one small thing that needs changing and a question.
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-06T18:29:55Z
user: login: ochromy
state: COMMENTED
author_association: NONE
submitted_at: 2025-05-12T04:33:56Z
user: login: jeana-redhat
body: Only a few issues here, repeated in similar contexts.

/remove-label merge-review-in-progress
/remove-label merge-review-needed
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T14:24:59Z
user: login: stevsmit
body: This LGTM. I only left one comment that is a slight suggestion, maybe to be done in the future. 
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-05-27T14:03:00Z

Review comments:
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving will wait for a revision to start sending network traffic after a request has been routed to it. The default is 300 seconds.
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+
+.Procedure
+
+* Choose the appropriate method to configure the revision response start timeout:
+** To configure the timeout globally, set the `revision-response-start-timeout-seconds` field in your `KnativeServing` custom resource (CR):
++
+.Example of revision response start timeout globally set to 600 seconds (10 minutes)
+[source,yaml]
+----
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+  namespace: knative-serving
+spec:
+  config:
+    defaults:
+      revision-response-start-timeout-seconds: "600"
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: maschmid
body: Setting just this would cause KnativeServing to fail, the controller would fail to start with this error:

> Error initializing apis config \"config-defaults\": \"revision-response-start-timeout-seconds (600) cannot be greater than revision-timeout-seconds (300)

The example should probably set both then, and we might want to add a note or a warning that `revision-response-start-timeout-seconds` cannot be greater than `revision-timeout-seconds` 
created_at: 2025-03-25T16:54:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving will wait for a revision to start sending network traffic after a request has been routed to it. The default is 300 seconds.
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+
+.Procedure
+
+* Choose the appropriate method to configure the revision response start timeout:
+** To configure the timeout globally, set the `revision-response-start-timeout-seconds` field in your `KnativeServing` custom resource (CR):
++
+.Example of revision response start timeout globally set to 600 seconds (10 minutes)
+[source,yaml]
+----
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+  namespace: knative-serving
+spec:
+  config:
+    defaults:
+      revision-response-start-timeout-seconds: "600"
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: ochromy
body: Thanks! I've pushed the updated version.
created_at: 2025-03-27T10:06:20Z
author_association: NONE
diff_hunk: @@ -0,0 +1,51 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving will wait for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds.
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+
+.Procedure
+
+* Choose the appropriate method to configure the revision response start timeout:
+** To configure the timeout globally, set the `revision-response-start-timeout-seconds` field in your `KnativeServing` custom resource (CR). If your required response start timeout exceeds the revision timeout, also adjust `revision-timeout-seconds` accordingly:
++
+.Example of revision response start timeout globally set to 600 seconds (10 minutes)
+[source,yaml]
+----
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+  namespace: knative-serving
+spec:
+  config:
+    defaults:
+      revision-timeout-seconds: "900"
+      revision-response-start-timeout-seconds: "600"
+----
++
+** To configure the timeout per revision, set the `responseStartTimeoutSeconds` field in your service definition. If your required response start timeout exceeds the revision timeout, also adjust `timeoutSeconds` accordingly:
++
+.Example of a service definition with revision response start timeout set to 600 seconds (10 minutes)
+[source,yaml]
+----
+apiVersion: serving.knative.dev/v1
+kind: Service
+metadata:
+  namespace: my-ns
+spec:
+  template:
+    spec:
+      timeoutSeconds: 900
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: maschmid
body: Creating this with a default KnativeServing config would fail 
```
Error from server (BadRequest): error when creating "./idle.yaml": admission webhook "validation.webhook.serving.knative.dev" denied the request: validation failed: expected 0 <= 900 <= 600: spec.template.spec.timeoutSeconds
```

you'd have to increase the `max-revision-timeout-seconds` setting in KnativeServing 

```
apiVersion: operator.knative.dev/v1beta1
kind: KnativeServing
metadata:
  name: knative-serving
  namespace: knative-serving
spec:
  config:
    defaults:
      max-revision-timeout-seconds: "900"
```

also, to actually fully use the timeoutSeconds, either the global ROUTE_HAPROXY_TIMEOUT serverless env would have to be set, or the `serving.knative.openshift.io/setRouteTimeout: "900"`  annotation added to the knative Service (not the revision template),  both of these are described in https://github.com/openshift/openshift-docs/pull/89935/files 
created_at: 2025-03-27T10:10:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,51 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving will wait for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds.
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+
+.Procedure
+
+* Choose the appropriate method to configure the revision response start timeout:
+** To configure the timeout globally, set the `revision-response-start-timeout-seconds` field in your `KnativeServing` custom resource (CR). If your required response start timeout exceeds the revision timeout, also adjust `revision-timeout-seconds` accordingly:
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: lahinson
body: ```suggestion
** To configure the timeout globally, set the `revision-response-start-timeout-seconds` field in your `KnativeServing` custom resource (CR). If your required response start timeout exceeds the revision timeout, also adjust the `revision-timeout-seconds` field accordingly:
```
created_at: 2025-03-27T14:25:41Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,51 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving will wait for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds.
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+
+.Procedure
+
+* Choose the appropriate method to configure the revision response start timeout:
+** To configure the timeout globally, set the `revision-response-start-timeout-seconds` field in your `KnativeServing` custom resource (CR). If your required response start timeout exceeds the revision timeout, also adjust `revision-timeout-seconds` accordingly:
++
+.Example of revision response start timeout globally set to 600 seconds (10 minutes)
+[source,yaml]
+----
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+  namespace: knative-serving
+spec:
+  config:
+    defaults:
+      revision-timeout-seconds: "900"
+      revision-response-start-timeout-seconds: "600"
+----
++
+** To configure the timeout per revision, set the `responseStartTimeoutSeconds` field in your service definition. If your required response start timeout exceeds the revision timeout, also adjust `timeoutSeconds` accordingly:
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: lahinson
body: ```suggestion
** To configure the timeout per revision, set the `responseStartTimeoutSeconds` field in your service definition. If your required response start timeout exceeds the revision timeout, also adjust the `timeoutSeconds` field accordingly:
```
created_at: 2025-03-27T14:27:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="configuring-maximum-revision-timeout_{context}"]
 = Configuring maximum revision timeout
 
-By seting the maximum revision timeout, you can ensure that no revision can exceed a specific limit.
+By seting the maximum revision timeout, you can ensure that no revision can exceed a specific limit. The value of your maximum revision timeout must not exceed the `terminationGracePeriodSeconds` of the activator to prevent in-flight requests being disrupted.
path: modules/configuring-maximum-revision-timeout.adoc
user: login: xenolinux
body: ```suggestion
By seting the maximum revision timeout, you can ensure that no revision can exceed a specific limit. The value of your maximum revision timeout must not exceed the `terminationGracePeriodSeconds` value of the activator to prevent in-flight requests being disrupted.
```

Object name is required. 
- See https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/doc_guidelines.adoc#object-references
created_at: 2025-04-08T07:52:52Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,59 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving will wait for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds (5 minutes).
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: xenolinux
body: ```suggestion
By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving waits for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds (5 minutes).
```
created_at: 2025-04-08T07:53:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,59 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving will wait for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds (5 minutes).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: xenolinux
body: ```suggestion
* You have cluster administrator permissions on {ocp-product-title}. Alternatively, cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
```

To avoid multiple conjunctions "or".
created_at: 2025-04-08T07:57:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_content-type: PROCEDURE
+[id="serverless-configuring-revision-idle-timeout_{context}"]
+= Configuring revision idle timeout
+
+By setting the revision idle timeout, you can specify the maximum duration in seconds a request is allowed to stay open without receiving data from the application. The default is `0` (infinite).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/serverless-configuring-revision-idle-timeout.adoc
user: login: xenolinux
body: Same comment as earlier
created_at: 2025-04-08T08:02:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,26 +1,21 @@
 // Module included in the following assemblies:
 //
 // * knative-serving/config-applications/configuring-revision-timeouts.adoc
-:_content-type: PROCEDURE
+:_mod-docs-content-type: PROCEDURE
 [id="configuring-maximum-revision-timeout_{context}"]
 = Configuring maximum revision timeout
 
-By seting the maximum revision timeout, you can ensure that no revision can exceed a specific limit.
+By seting the maximum revision timeout, you can ensure that no revision can exceed a specific limit. The value of your maximum revision timeout must not exceed the `terminationGracePeriodSeconds` value of the activator to prevent in-flight requests being disrupted.
 
 .Prerequisites
 
 * You have installed the {ServerlessOperatorName} and Knative Serving.
-* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/configuring-maximum-revision-timeout.adoc
user: login: kcarmichael08
body: With this edit, the second sentence is now a sentence fragment and needs a verb. For example:

"Alternatively, you have cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}."

created_at: 2025-05-06T18:21:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -10,7 +10,7 @@ You can configure the default number of seconds for the revision timeout based o
 .Prerequisites
 
 * You have installed the {ServerlessOperatorName} and Knative Serving.
-* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/configuring-revision-timeout.adoc
user: login: kcarmichael08
body: see previous comment about sentence fragment
created_at: 2025-05-06T18:23:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,59 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving waits for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds (5 minutes).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: kcarmichael08
body: See previous comment about sentence fragment.
created_at: 2025-05-06T18:23:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-revision-idle-timeout_{context}"]
+= Configuring revision idle timeout
+
+By setting the revision idle timeout, you can specify the maximum duration in seconds a request is allowed to stay open without receiving data from the application. The default is `0` (infinite).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/serverless-configuring-revision-idle-timeout.adoc
user: login: kcarmichael08
body: see previous comment
created_at: 2025-05-06T18:24:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -33,3 +28,11 @@ spec:
     defaults:
       max-revision-timeout-seconds: "600"
 ----
+
++
+[NOTE]
+====
+To set the maximum revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout. 
+
+For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long Running Requests".
path: modules/configuring-maximum-revision-timeout.adoc
user: login: kcarmichael08
body: I might be missing something, but I don't see anything on this page for "Long Running Requests". Will the user know where to find that information? 
created_at: 2025-05-06T18:28:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -33,3 +28,11 @@ spec:
     defaults:
       max-revision-timeout-seconds: "600"
 ----
+
++
+[NOTE]
+====
+To set the maximum revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout. 
+
+For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long Running Requests".
path: modules/configuring-maximum-revision-timeout.adoc
user: login: ochromy
body: Hi @kcarmichael08, "Long Running Requests" is being added simultaneously with this update as part of https://github.com/openshift/openshift-docs/pull/89935 and should be merged before SRVKS-1289 (additional info in the PR desc).
created_at: 2025-05-12T04:33:55Z
author_association: NONE
diff_hunk: @@ -0,0 +1,59 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: jeana-redhat
body: Per templates, should be a line here
```suggestion
// * knative-serving/config-applications/configuring-revision-timeouts.adoc

:_mod-docs-content-type: PROCEDURE
```
created_at: 2025-05-13T13:02:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,59 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving waits for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds (5 minutes).
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: jeana-redhat
body: ```suggestion
By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving waits for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default duration is 300 seconds (5 minutes).
```
created_at: 2025-05-13T13:12:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,59 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving waits for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds (5 minutes).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, you have cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: jeana-redhat
body: This is not clear.

It can read as either:
```
* You have the required permissions for your cluster:
** Cluster administrator permissions on {ocp-product-title}
** Cluster administrator or dedicated administrator permissions on {rosa-product-title}
** Cluster administrator or dedicated administrator permissions on {dedicated-product-title}
```

or:
```
* You have the required permissions for your cluster:
** Cluster administrator permissions on {ocp-product-title}
** Cluster administrator permissions on {rosa-product-title}
** Dedicated administrator permissions on {dedicated-product-title}
```

I think it probably is meant the second way, but I am not confident because the sentence could be read either way. Suggest breaking each cluster type out and stating what it needs. Since there are three options, a list is easier to scan for the cluster the user cares about.
created_at: 2025-05-13T13:16:52Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,59 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving waits for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds (5 minutes).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, you have cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+
+.Procedure
+
+* Choose the appropriate method to configure the revision response start timeout:
+** To configure the timeout globally, set the `revision-response-start-timeout-seconds` field in your `KnativeServing` custom resource (CR). If your required response start timeout exceeds the revision timeout, also adjust the `revision-timeout-seconds` field accordingly:
++
+.Example of revision response start timeout globally set to 300 seconds (5 minutes)
+[source,yaml]
+----
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+  namespace: knative-serving
+spec:
+  config:
+    defaults:
+      revision-timeout-seconds: "600"
+      revision-response-start-timeout-seconds: "300"
+----
++
+** To configure the timeout per revision, set the `responseStartTimeoutSeconds` field in your service definition. If your required response start timeout exceeds the revision timeout, also adjust the `timeoutSeconds` field accordingly:
++
+.Example of a service definition with revision response start timeout set to 300 seconds (5 minutes)
+[source,yaml]
+----
+apiVersion: serving.knative.dev/v1
+kind: Service
+metadata:
+  namespace: my-ns
+spec:
+  template:
+    spec:
+      timeoutSeconds: 600
+      responseStartTimeoutSeconds: 300
+      containers:
+# ...
+----
+
++
+[NOTE]
+====
+To set the revision response start timeout and the revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout and the maximum revision timeout. 
+
+For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long Running Requests".
+====
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: jeana-redhat
body: If this is important to know, consider moving it to the introduction of the task. Someone using the first option might skip over this since they are skipping the second option, but it applies to either case.
created_at: 2025-05-13T14:17:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
path: modules/serverless-configuring-revision-idle-timeout.adoc
user: login: jeana-redhat
body: ```suggestion
// * knative-serving/config-applications/configuring-revision-timeouts.adoc

:_mod-docs-content-type: PROCEDURE
```
created_at: 2025-05-13T14:17:12Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-revision-idle-timeout_{context}"]
+= Configuring revision idle timeout
+
+By setting the revision idle timeout, you can specify the maximum duration in seconds a request is allowed to stay open without receiving data from the application. The default is `0` (infinite).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, you have cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/serverless-configuring-revision-idle-timeout.adoc
user: login: jeana-redhat
body: Same comment as in the previous task
created_at: 2025-05-13T14:17:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-revision-idle-timeout_{context}"]
+= Configuring revision idle timeout
+
+By setting the revision idle timeout, you can specify the maximum duration in seconds a request is allowed to stay open without receiving data from the application. The default is `0` (infinite).
path: modules/serverless-configuring-revision-idle-timeout.adoc
user: login: jeana-redhat
body: ```suggestion
By setting the revision idle timeout, you can specify the maximum duration in seconds a request is allowed to stay open without receiving data from the application. The default duration is `0` (infinite).
```
created_at: 2025-05-13T14:17:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,7 +1,7 @@
 // Module included in the following assemblies:
 //
 // * knative-serving/config-applications/configuring-revision-timeouts.adoc
-:_content-type: PROCEDURE
+:_mod-docs-content-type: PROCEDURE
path: modules/configuring-revision-timeout.adoc
user: login: jeana-redhat
body: existing content, but there should be a blank line after the assembly list
```suggestion

:_mod-docs-content-type: PROCEDURE
```
created_at: 2025-05-13T14:19:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -10,7 +10,7 @@ You can configure the default number of seconds for the revision timeout based o
 .Prerequisites
 
 * You have installed the {ServerlessOperatorName} and Knative Serving.
-* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, you have cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/configuring-revision-timeout.adoc
user: login: jeana-redhat
body: Same comment as for the other modules
created_at: 2025-05-13T14:19:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -45,3 +45,11 @@ spec:
       containers:
       - image: ghcr.io/knative/helloworld-go:latest
 ----
+
++
+[NOTE]
+====
+To set the revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout and the maximum revision timeout. 
+
+For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long Running Requests".
+====
path: modules/configuring-revision-timeout.adoc
user: login: jeana-redhat
body: Same comment about this note placement as earlier
created_at: 2025-05-13T14:19:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -33,3 +28,11 @@ spec:
     defaults:
       max-revision-timeout-seconds: "600"
 ----
+
++
+[NOTE]
path: modules/configuring-maximum-revision-timeout.adoc
user: login: jeana-redhat
body: Same comment about placement as earlier
created_at: 2025-05-13T14:20:12Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,26 +1,21 @@
 // Module included in the following assemblies:
 //
 // * knative-serving/config-applications/configuring-revision-timeouts.adoc
-:_content-type: PROCEDURE
+:_mod-docs-content-type: PROCEDURE
path: modules/configuring-maximum-revision-timeout.adoc
user: login: jeana-redhat
body: ```suggestion

:_mod-docs-content-type: PROCEDURE
```
created_at: 2025-05-13T14:20:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,26 +1,21 @@
 // Module included in the following assemblies:
 //
 // * knative-serving/config-applications/configuring-revision-timeouts.adoc
-:_content-type: PROCEDURE
+:_mod-docs-content-type: PROCEDURE
 [id="configuring-maximum-revision-timeout_{context}"]
 = Configuring maximum revision timeout
 
-By seting the maximum revision timeout, you can ensure that no revision can exceed a specific limit.
+By seting the maximum revision timeout, you can ensure that no revision can exceed a specific limit. The value of your maximum revision timeout must not exceed the `terminationGracePeriodSeconds` value of the activator to prevent in-flight requests being disrupted.
 
 .Prerequisites
 
 * You have installed the {ServerlessOperatorName} and Knative Serving.
-* You have cluster administrator permissions on {ocp-product-title}, or cluster or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, you have cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
path: modules/configuring-maximum-revision-timeout.adoc
user: login: jeana-redhat
body: Same comment on this as earlier
created_at: 2025-05-13T14:20:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,59 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-resoponse-start-timeout_{context}"]
+= Configuring revision response start timeout
+
+By setting the revision response start timeout, you can specify the maximum duration in seconds that Serving waits for a revision to start sending network traffic after a request has been routed to it. The revision response start timeout must not exceed the revision timeout. The default is 300 seconds (5 minutes).
+
+.Prerequisites
+
+* You have installed the {ServerlessOperatorName} and Knative Serving.
+* You have cluster administrator permissions on {ocp-product-title}. Alternatively, you have cluster administrator or dedicated administrator permissions on {rosa-product-title} or {dedicated-product-title}.
+
+.Procedure
+
+* Choose the appropriate method to configure the revision response start timeout:
+** To configure the timeout globally, set the `revision-response-start-timeout-seconds` field in your `KnativeServing` custom resource (CR). If your required response start timeout exceeds the revision timeout, also adjust the `revision-timeout-seconds` field accordingly:
++
+.Example of revision response start timeout globally set to 300 seconds (5 minutes)
+[source,yaml]
+----
+apiVersion: operator.knative.dev/v1beta1
+kind: KnativeServing
+metadata:
+  name: knative-serving
+  namespace: knative-serving
+spec:
+  config:
+    defaults:
+      revision-timeout-seconds: "600"
+      revision-response-start-timeout-seconds: "300"
+----
++
+** To configure the timeout per revision, set the `responseStartTimeoutSeconds` field in your service definition. If your required response start timeout exceeds the revision timeout, also adjust the `timeoutSeconds` field accordingly:
++
+.Example of a service definition with revision response start timeout set to 300 seconds (5 minutes)
+[source,yaml]
+----
+apiVersion: serving.knative.dev/v1
+kind: Service
+metadata:
+  namespace: my-ns
+spec:
+  template:
+    spec:
+      timeoutSeconds: 600
+      responseStartTimeoutSeconds: 300
+      containers:
+# ...
+----
+
++
+[NOTE]
+====
+To set the revision response start timeout and the revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout and the maximum revision timeout. 
+
+For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long Running Requests".
path: modules/serverless-configuring-response-start-timeout.adoc
user: login: jeana-redhat
body: (applies to all instance of this note - btw, might be a good place for a snippet so you only have one place to edit it?) 

The topic is capitalized as follows:
```suggestion
For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long running requests".
```

However, "long-running" is a compound adjective, so ideally the note and the title itself should be updated to:
```suggestion
For instructions on how to configure timeouts for requests exceeding the default 600 seconds (10 minutes), see "Long-running requests".
```
created_at: 2025-05-13T14:23:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,53 @@
+// Module included in the following assemblies:
+//
+// * knative-serving/config-applications/configuring-revision-timeouts.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="serverless-configuring-revision-idle-timeout_{context}"]
+= Configuring revision idle timeout
+
+By setting the revision idle timeout, you can specify the maximum duration in seconds a request is allowed to stay open without receiving data from the application. The default duration is `0` (infinite).
path: modules/serverless-configuring-revision-idle-timeout.adoc
user: login: stevsmit
body: If you ever revise this module, adding "that" could really help clarify this sentence. You also used it in the other module (eg, ". . . duration in seconds that Serving waits. . .")

I also added some commas to break up the sentence a little bit, but they're not necessary. This will not hold up merge review.

```suggestion
By setting the revision idle timeout, you can specify the maximum duration, in seconds, that a request is allowed to stay open without receiving data from the application. The default duration is `0` (infinite).
```
created_at: 2025-05-27T13:58:18Z
author_association: MEMBER

PR comments:
user: login: openshift-ci[bot]
created_at: 2025-02-19T12:22:15Z
body: Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with `/test all`
author_association: NONE
user: login: ocpdocs-previewbot
created_at: 2025-03-01T12:13:47Z
body: 🤖 Mon May 26 06:43:23 - Prow CI generated the docs preview:

https://88871--ocpdocs-pr.netlify.app/openshift-serverless/latest/knative-serving/config-applications/configuring-revision-timeouts.html
author_association: NONE
user: login: ochromy
created_at: 2025-03-27T10:06:47Z
body: /label serverless
/label peer-review-needed
author_association: NONE
user: login: ochromy
created_at: 2025-04-08T07:28:09Z
body: Requesting a peer review again as I've expanded the content. 
@lahinson Thanks for the initial one!

/label peer-review-needed
author_association: NONE
user: login: ochromy
created_at: 2025-05-06T05:15:53Z
body: /label merge-review-needed
author_association: NONE
user: login: ochromy
created_at: 2025-05-13T06:08:11Z
body: Thanks @kcarmichael08

/label merge-review-needed
author_association: NONE
user: login: openshift-ci[bot]
created_at: 2025-05-26T06:44:10Z
body: @ochromy: all tests **passed!**


[Full PR test history](https://prow.ci.openshift.org/pr-history?org=openshift&repo=openshift-docs&pr=88871). [Your PR dashboard](https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:ochromy).

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
author_association: NONE
user: login: ochromy
created_at: 2025-05-26T06:48:15Z
body: Thanks @jeana-redhat 

/label merge-review-needed
author_association: NONE
user: login: stevsmit
created_at: 2025-05-27T14:10:23Z
body: /cherry-pick serverless-docs-1.34
author_association: MEMBER
user: login: stevsmit
created_at: 2025-05-27T14:10:27Z
body: /cherry-pick serverless-docs-1.35
author_association: MEMBER
user: login: stevsmit
created_at: 2025-05-27T14:10:31Z
body: /cherry-pick serverless-docs-1.36
author_association: MEMBER
user: login: openshift-cherrypick-robot
created_at: 2025-05-27T14:11:22Z
body: @stevsmit: #88871 failed to apply on top of branch "serverless-docs-1.34":
```
Applying: Timeout seconds for revisions - follow up
.git/rebase-apply/patch:75: trailing whitespace.
To set the maximum revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout. 
.git/rebase-apply/patch:113: trailing whitespace.
To set the revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout and the maximum revision timeout. 
.git/rebase-apply/patch:182: trailing whitespace.
To set the revision response start timeout and the revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout and the maximum revision timeout. 
warning: 3 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	knative-serving/config-applications/configuring-revision-timeouts.adoc
A	modules/serverless-long-running-requests.adoc
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): modules/serverless-long-running-requests.adoc deleted in HEAD and modified in Timeout seconds for revisions - follow up. Version Timeout seconds for revisions - follow up of modules/serverless-long-running-requests.adoc left in tree.
Auto-merging knative-serving/config-applications/configuring-revision-timeouts.adoc
CONFLICT (content): Merge conflict in knative-serving/config-applications/configuring-revision-timeouts.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Timeout seconds for revisions - follow up

```

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/88871#issuecomment-2912663492):

>/cherry-pick serverless-docs-1.34


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-05-27T14:11:28Z
body: @stevsmit: #88871 failed to apply on top of branch "serverless-docs-1.35":
```
Applying: Timeout seconds for revisions - follow up
.git/rebase-apply/patch:75: trailing whitespace.
To set the maximum revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout. 
.git/rebase-apply/patch:113: trailing whitespace.
To set the revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout and the maximum revision timeout. 
.git/rebase-apply/patch:182: trailing whitespace.
To set the revision response start timeout and the revision timeout to a value over 600 seconds (10 minutes), you must increase the default {ocp-product-title} route timeout and the maximum revision timeout. 
warning: 3 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	knative-serving/config-applications/configuring-revision-timeouts.adoc
A	modules/serverless-long-running-requests.adoc
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): modules/serverless-long-running-requests.adoc deleted in HEAD and modified in Timeout seconds for revisions - follow up. Version Timeout seconds for revisions - follow up of modules/serverless-long-running-requests.adoc left in tree.
Auto-merging knative-serving/config-applications/configuring-revision-timeouts.adoc
CONFLICT (content): Merge conflict in knative-serving/config-applications/configuring-revision-timeouts.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Timeout seconds for revisions - follow up

```

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/88871#issuecomment-2912663720):

>/cherry-pick serverless-docs-1.35


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-05-27T14:11:43Z
body: @stevsmit: new pull request created: #93766

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/88871#issuecomment-2912663938):

>/cherry-pick serverless-docs-1.36


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE