Skip to content

OCPBUGS-31432: Added user-managed LB prereq to said documents #102959

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −4
Open

OCPBUGS-31432: Added user-managed LB prereq to said documents #102959

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions modules/nw-autoscaling-ingress-controller.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ The following procedure provides an example for scaling up the default Ingress C

* You have the {oc-first} installed.
* You have access to an {product-title} cluster as a user with the `cluster-admin` role.
* On {vmw-first}, bare-metal, and Nutanix installer-provisioned infrastructure, scaling up Ingress Controller pods does not improve external traffic performance. To improve performance, you must manually configure a user-managed load balancer for your cluster and the load balancer must know what cluster nodes handle incoming traffic from the Ingress Controller.
* You installed the Custom Metrics Autoscaler Operator and an associated KEDA Controller.
** 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`.

Expand Down Expand Up @@ -191,6 +192,7 @@ $ oc apply -f ingress-autoscaler.yaml
----

.Verification

* 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:

** Use the `grep` command to search the Ingress Controller YAML file for the number of replicas:
Expand Down
10 changes: 6 additions & 4 deletions modules/nw-scaling-ingress-controller.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,17 +6,19 @@
[id="nw-ingress-controller-configuration_{context}"]
= Scaling an Ingress Controller

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
procedure provides an example for scaling up the default `IngressController`.
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 procedure provides an example for scaling up the default `IngressController`.

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

.Prerequisites

* On {vmw-first}, bare-metal Nutanix installer-provisioned infrastructure, scaling up Ingress Controller pods does not improve external traffic performance. To improve performance, you must manually configure a user-managed load balancer for your cluster and the load balancer must know what cluster nodes handle incoming traffic from the Ingress Controller.

.Procedure

. View the current number of available replicas for the default `IngressController`:
+
[source,terminal]
Expand Down