From 178e286f850f8c4033c20e689a07908419dc8f4b Mon Sep 17 00:00:00 2001 From: Ondrej Chromy Date: Fri, 16 May 2025 16:01:10 +0200 Subject: [PATCH] [SRVKS-1303] haproxy.router.openshift.io/timeout config for auto-created routes fix yaml truncation --- .../configuring-service-routes.adoc | 7 +++++- ...uring-default-route-timeouts-globally.adoc | 22 +++++++++++++++++-- 2 files changed, 26 insertions(+), 3 deletions(-) diff --git a/knative-serving/external-ingress-routing/configuring-service-routes.adoc b/knative-serving/external-ingress-routing/configuring-service-routes.adoc index 1ed99dfb870c..095675aed88f 100644 --- a/knative-serving/external-ingress-routing/configuring-service-routes.adoc +++ b/knative-serving/external-ingress-routing/configuring-service-routes.adoc @@ -12,4 +12,9 @@ If you want to configure a Knative service to use your TLS certificate on {ocp-p When you complete the following procedure, the default {ocp-product-title} route in the `knative-serving-ingress` namespace is not created. However, the Knative route for the application is still created in this namespace. ==== -include::modules/serverless-openshift-routes.adoc[leveloffset=+1] \ No newline at end of file +include::modules/serverless-openshift-routes.adoc[leveloffset=+1] + +[NOTE] +==== +You can also set the default timeout value for auto-generated {ocp-product-title} routes. See xref:../../config-applications/modules/configuring-default-route-timeouts-globally.adoc[Configuring the default route timeouts]. +==== diff --git a/modules/configuring-default-route-timeouts-globally.adoc b/modules/configuring-default-route-timeouts-globally.adoc index 7846d4ba6e7b..0d2916e6c35b 100644 --- a/modules/configuring-default-route-timeouts-globally.adoc +++ b/modules/configuring-default-route-timeouts-globally.adoc @@ -12,7 +12,7 @@ You can configure the route timeouts globally by updating the `ROUTE_HAPROXY_TIM .Procedure -. Set the value of `ROUTE_HAPROXY_TIMEOUT` in your subscription to your required timeout in seconds by running the following command: +. Set the value of `ROUTE_HAPROXY_TIMEOUT` in your subscription to your required timeout in seconds by running the following command. Note that this causes pods to be redeployed in the `openshift-serverless` namespace. + .Setting the `ROUTE_HAPROXY_TIMEOUT` value to 900 seconds [source,terminal] @@ -20,7 +20,25 @@ You can configure the route timeouts globally by updating the `ROUTE_HAPROXY_TIM $ oc patch subscription.operators.coreos.com serverless-operator -n openshift-serverless --type='merge' -p '{"spec": {"config": {"env": [{"name": "ROUTE_HAPROXY_TIMEOUT", "value": "900"}]}}}' ---- + -The `ROUTE_HAPROXY_TIMEOUT` environment variable is managed by the Serverless Operator and by default is set to `600`. Set the value of `ROUTE_HAPROXY_TIMEOUT` in your subscription to your required timeout in seconds by running the following command. Note that this causes pods to be redeployed in the `openshift-serverless` namespace. +Alternatively, you can set the value of `ROUTE_HAPROXY_TIMEOUT` in your subscription directly: ++ +.A subscription definition with `ROUTE_HAPROXY_TIMEOUT` set to 900 seconds +[source,yaml] +---- +apiVersion: operators.coreos.com/v1alpha1 +kind: Subscription +metadata: +#... +spec: + channel: stable + config: + env: + - name: ROUTE_HAPROXY_TIMEOUT + value: '900' +#... +---- ++ +The `ROUTE_HAPROXY_TIMEOUT` environment variable is managed by the Serverless Operator and by default is set to `600`. + [NOTE] ====