Skip to content

Commit ee757d4

Browse files
committed
OCPBUGS-31432: Added user-managed LB prereq to said documents
1 parent 317c25b commit ee757d4

File tree

2 files changed

+8
-3
lines changed

2 files changed

+8
-3
lines changed

modules/nw-autoscaling-ingress-controller.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ The following procedure provides an example for scaling up the default Ingress C
1414

1515
* You have the {oc-first} installed.
1616
* You have access to an {product-title} cluster as a user with the `cluster-admin` role.
17+
* {vmw-first} or bare-metal infrastructure only: You configured a user-managed load balancer for your cluster.
1718
* You installed the Custom Metrics Autoscaler Operator and an associated KEDA Controller.
1819
** You can install the Operator by using the software catalog on the web console. After you install the Operator, you can create an instance of `KedaController`.
1920
@@ -191,6 +192,7 @@ $ oc apply -f ingress-autoscaler.yaml
191192
----
192193

193194
.Verification
195+
194196
* Verify that the default Ingress Controller is scaled out to match the value returned by the `kube-state-metrics` query by running the following commands:
195197
196198
** Use the `grep` command to search the Ingress Controller YAML file for the number of replicas:

modules/nw-scaling-ingress-controller.adoc

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,20 @@
66
[id="nw-ingress-controller-configuration_{context}"]
77
= Scaling an Ingress Controller
88

9-
Manually scale an Ingress Controller to meeting routing performance or
10-
availability requirements such as the requirement to increase throughput. `oc`
11-
commands are used to scale the `IngressController` resource. The following
9+
Manually scale an Ingress Controller to meeting routing performance or availability requirements such as the requirement to increase throughput. `oc` commands are used to scale the `IngressController` resource. The following
1210
procedure provides an example for scaling up the default `IngressController`.
1311

1412
[NOTE]
1513
====
1614
Scaling is not an immediate action, as it takes time to create the desired number of replicas.
1715
====
1816

17+
.Prerequisites
18+
19+
* {vmw-first} or bare-metal infrastructure only: You configured a user-managed load balancer for your cluster.
20+
1921
.Procedure
22+
2023
. View the current number of available replicas for the default `IngressController`:
2124
+
2225
[source,terminal]

0 commit comments

Comments
 (0)