Skip to content

OCPBUGS-64635 added note to document #104233

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
wgabor0427 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

OCPBUGS-64635 added note to document #104233

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
19 changes: 12 additions & 7 deletions modules/installation-two-node-ingress-lb-configuration.adoc
View file
Open in desktop
Copy link
Collaborator

@ocpdocs-vale-bot ocpdocs-vale-bot Dec 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] AsciiDocDITA.ShortDescription: Assign [role="_abstract"] to a paragraph to use it as in DITA.

Copy link
Contributor Author

@wgabor0427 wgabor0427 Dec 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Original file line number Diff line number Diff line change
Expand Up @@ -2,27 +2,32 @@
[id="two-node-ingress-lb-configuration_{context}"]
= Configuring an Ingress load balancer for a two-node cluster with fencing

You must configure an external Ingress load balancer (LB) before you install a two-node OpenShift cluster with fencing. The Ingress LB forwards external application traffic to the Ingress Controller pods that run on the control plane nodes. Both nodes can actively receive traffic.
[role="_abstract"]
Configure an external Ingress load balancer to forward application traffic to Ingress Controller pods on control plane nodes. You must configure this load balancer before installing a two-node OpenShift cluster with fencing to allow both nodes to actively receive traffic.

[NOTE]
====
An external load balancer is recommended for production deployments but is not required.
====

.Prerequisites

* You have two control plane nodes with fencing enabled.
* You have network connectivity from the load balancer to both control plane nodes.
* You created DNS records for `api.<cluster_name>.<base_domain>` and `*.apps.<cluster_name>.<base_domain>`.
* You have an external load balancer that supports health checks on endpoints.
* You have two control plane nodes with fencing enabled.
* You have network connectivity from the load balancer to both control plane nodes.
* You created DNS records for `api.<cluster_name>.<base_domain>` and `*.apps.<cluster_name>.<base_domain>`.

.Procedure

. Configure the load balancer to forward traffic for the following ports:
+
* `6443`: Kubernetes API server
* `6443`: Kubernetes API server
* `80` and `443`: Application ingress
+
You must forward traffic to both control plane nodes.

. Configure health checks on the load balancer. You must monitor the backend endpoints so that the load balancer only sends traffic to nodes that respond.

. Configure the load balancer to forward traffic to both control plane nodes. The following example shows how to configure two control plane nodes:
. Configure the load balancer to forward traffic to both control plane nodes. The following example shows how to configure two control plane nodes:
+
[source,terminal]
----
Expand Down