From f1c3e78058bc0b8e25c2bc66e4cd6dad567402c0 Mon Sep 17 00:00:00 2001 From: Atharva Shinde Date: Tue, 26 Nov 2024 18:55:35 +0530 Subject: [PATCH 1/2] OCPBUGS#45054: Maintain linear nomenclature for nodes in the examples of the platform agnostic cluster installation documentation --- .../installation-load-balancing-user-infra.adoc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/modules/installation-load-balancing-user-infra.adoc b/modules/installation-load-balancing-user-infra.adoc index 3bf5b5957731..b7e4c29a3e8c 100644 --- a/modules/installation-load-balancing-user-infra.adoc +++ b/modules/installation-load-balancing-user-infra.adoc @@ -145,7 +145,7 @@ ifdef::user-managed-lb[] This section provides an example API and application Ingress load balancer configuration that meets the load balancing requirements for clusters that are deployed with user-managed load balancers. The sample is an `/etc/haproxy/haproxy.cfg` configuration for an HAProxy load balancer. The example is not meant to provide advice for choosing one load balancing solution over another. endif::user-managed-lb[] -In the example, the same load balancer is used for the Kubernetes API and application ingress traffic. In production scenarios, you can deploy the API and application ingress load balancers separately so that you can scale the load balancer infrastructure for each in isolation. +In the example, the cluster name is `ocp4` and the base domain is `example.com`. Here, the same load balancer is used for the Kubernetes API and application ingress traffic. In production scenarios, you can deploy the API and application ingress load balancers separately so that you can scale the load balancer infrastructure for each in isolation. [NOTE] ==== @@ -184,16 +184,16 @@ listen api-server-6443 <1> option log-health-checks balance roundrobin server bootstrap bootstrap.ocp4.example.com:6443 verify none check check-ssl inter 10s fall 2 rise 3 backup <2> - server master0 master0.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3 - server master1 master1.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3 - server master2 master2.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3 + server control-plane0 control-plane0.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3 + server control-plane1 control-plane1.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3 + server control-plane2 control-plane2.ocp4.example.com:6443 weight 1 verify none check check-ssl inter 10s fall 2 rise 3 listen machine-config-server-22623 <3> bind *:22623 mode tcp server bootstrap bootstrap.ocp4.example.com:22623 check inter 1s backup <2> - server master0 master0.ocp4.example.com:22623 check inter 1s - server master1 master1.ocp4.example.com:22623 check inter 1s - server master2 master2.ocp4.example.com:22623 check inter 1s + server control-plane0 control-plane0.ocp4.example.com:22623 check inter 1s + server control-plane1 control-plane1.ocp4.example.com:22623 check inter 1s + server control-plane2 control-plane2.ocp4.example.com:22623 check inter 1s listen ingress-router-443 <4> bind *:443 mode tcp From 5f94619830ca89258e7cc4157f5f96a058ceaf1a Mon Sep 17 00:00:00 2001 From: Atharva Shinde Date: Tue, 3 Dec 2024 11:13:53 +0530 Subject: [PATCH 2/2] Update modules/installation-load-balancing-user-infra.adoc Co-authored-by: Alex Dellapenta --- modules/installation-load-balancing-user-infra.adoc | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/modules/installation-load-balancing-user-infra.adoc b/modules/installation-load-balancing-user-infra.adoc index b7e4c29a3e8c..1e28f844bc5f 100644 --- a/modules/installation-load-balancing-user-infra.adoc +++ b/modules/installation-load-balancing-user-infra.adoc @@ -145,7 +145,13 @@ ifdef::user-managed-lb[] This section provides an example API and application Ingress load balancer configuration that meets the load balancing requirements for clusters that are deployed with user-managed load balancers. The sample is an `/etc/haproxy/haproxy.cfg` configuration for an HAProxy load balancer. The example is not meant to provide advice for choosing one load balancing solution over another. endif::user-managed-lb[] -In the example, the cluster name is `ocp4` and the base domain is `example.com`. Here, the same load balancer is used for the Kubernetes API and application ingress traffic. In production scenarios, you can deploy the API and application ingress load balancers separately so that you can scale the load balancer infrastructure for each in isolation. +This example specifies the following: + +* The cluster name is `ocp4`. +* The base domain is `example.com`. +* The same load balancer is used for the Kubernetes API and application ingress traffic. + +In production scenarios, you can deploy the API and application ingress load balancers separately so that you can scale the load balancer infrastructure for each in isolation. [NOTE] ====