From b5d72ee174e3cb2cedeaf59b9439ec6d5b351ea9 Mon Sep 17 00:00:00 2001 From: hernanrivero Date: Fri, 12 Jan 2024 14:45:02 -0300 Subject: [PATCH 1/2] W-14773860 - Updating Traffic Management limits --- modules/ROOT/pages/create-instance-task-flex.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/create-instance-task-flex.adoc b/modules/ROOT/pages/create-instance-task-flex.adoc index 9fc5494cc..91d52be0a 100644 --- a/modules/ROOT/pages/create-instance-task-flex.adoc +++ b/modules/ROOT/pages/create-instance-task-flex.adoc @@ -54,7 +54,7 @@ image:multiple-upstreams.png[Flex Gateway manages the traffic to multiple upstre === Routes -Each API instance supports up to 10 routes and each route can support up to 10 upstream services. Configure what requests a route can receive by defining route rules and a route order. At least one route per API instance is required. +Each API instance supports up to 50 routes and each route can support up to 10 upstream services. Configure what requests a route can receive by defining route rules and a route order. At least one route per API instance is required. Before adding additional routes, enter an optional *Route label* for clarity. @@ -139,7 +139,7 @@ For example, in a configuration in which route one has the `GET` method defined You can use multiple upstream services in a single route to direct requests to similar services. For example, to test the performance of a new beta upstream service without sending all traffic to the new service, you can direct half of the traffic to a stable upstream service and half to the new upstream service. -Each API instance route can support up to 10 upstream services, but at least one upstream service is required for each route. +Each API instance route can support up to 50 upstream services, but at least one upstream service is required for each route. What upstream service within the route each request is sent to is random and independent of any previous request. The upstream *Weight* defines the percentage chance of a request being sent to a particular upstream service. From cc1856f3d971378e649a644780e4c2d8b32a4648 Mon Sep 17 00:00:00 2001 From: hernanrivero Date: Fri, 12 Jan 2024 14:47:35 -0300 Subject: [PATCH 2/2] Fix --- modules/ROOT/pages/create-instance-task-flex.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/create-instance-task-flex.adoc b/modules/ROOT/pages/create-instance-task-flex.adoc index 91d52be0a..9bdf335f9 100644 --- a/modules/ROOT/pages/create-instance-task-flex.adoc +++ b/modules/ROOT/pages/create-instance-task-flex.adoc @@ -54,7 +54,7 @@ image:multiple-upstreams.png[Flex Gateway manages the traffic to multiple upstre === Routes -Each API instance supports up to 50 routes and each route can support up to 10 upstream services. Configure what requests a route can receive by defining route rules and a route order. At least one route per API instance is required. +Each API instance supports up to 50 routes and each route can support up to 10 upstream services. Configure what requests a route can receive by defining route rules and a route order. At least one route per API instance is required. Before adding additional routes, enter an optional *Route label* for clarity. @@ -139,7 +139,7 @@ For example, in a configuration in which route one has the `GET` method defined You can use multiple upstream services in a single route to direct requests to similar services. For example, to test the performance of a new beta upstream service without sending all traffic to the new service, you can direct half of the traffic to a stable upstream service and half to the new upstream service. -Each API instance route can support up to 50 upstream services, but at least one upstream service is required for each route. +Each API instance route can support up to 50 upstream services, but at least one upstream service is required for each route. What upstream service within the route each request is sent to is random and independent of any previous request. The upstream *Weight* defines the percentage chance of a request being sent to a particular upstream service.