I followed same steps to configure OCP4-Metal-install and I successfully configured the cluster with 3 control plane nodes and two worker nodes.
I added additional node to the cluster successfully but the status in not updating in HA-proxy. any changes do I need to perform in HA-Proxy. any support is much appreciated.
[root@ocp-svc log]# oc get nodes
NAME STATUS ROLES AGE VERSION
ocp-cp-1.lab.ocp.lan Ready control-plane,master,worker 28h v1.27.8+4fab27b
ocp-cp-2.lab.ocp.lan Ready control-plane,master,worker 27h v1.27.8+4fab27b
ocp-cp-3.lab.ocp.lan Ready control-plane,master,worker 27h v1.27.8+4fab27b
ocp-w-1.lab.ocp.lan Ready worker 26h v1.27.8+4fab27b
ocp-w-2.lab.ocp.lan Ready worker 26h v1.27.8+4fab27b
ocp-w-3.lab.ocp.lan Ready worker 7h37m v1.27.8+4fab27b
ocp-w-4.lab.ocp.lan Ready worker 7h17m v1.27.8+4fab27b
[root@ocp-svc log]#
[root@ocp-svc log]#
[root@ocp-svc log]#
my Haproxy configuration:
[root@ocp-svc ocp-install]# cat /etc/haproxy/haproxy.cfg
Global settings
#---------------------------------------------------------------------
global
maxconn 20000
log /dev/log local0 info
chroot /var/lib/haproxy
pidfile /var/run/haproxy.pid
user haproxy
group haproxy
daemon
# turn on stats unix socket
stats socket /var/lib/haproxy/stats
#---------------------------------------------------------------------
common defaults that all the ‘listen’ and ‘backend’ sections will
use if not designated in their block
#---------------------------------------------------------------------
defaults
log global
mode http
option httplog
option dontlognull
option http-server-close
option redispatch
option forwardfor except 127.0.0.0/8
retries 3
maxconn 20000
timeout http-request 10000ms
timeout http-keep-alive 10000ms
timeout check 10000ms
timeout connect 40000ms
timeout client 300000ms
timeout server 300000ms
timeout queue 50000ms
Enable HAProxy stats
listen stats
bind :9000
stats uri /stats
stats refresh 10000ms
Kube API Server
frontend k8s_api_frontend
bind :6443
default_backend k8s_api_backend
mode tcp
backend k8s_api_backend
mode tcp
balance source
server ocp-bootstrap 192.168.22.200:6443 check
server ocp-cp-1 192.168.22.201:6443 check
server ocp-cp-2 192.168.22.202:6443 check
server ocp-cp-3 192.168.22.203:6443 check
OCP Machine Config Server
frontend ocp_machine_config_server_frontend
mode tcp
bind :22623
default_backend ocp_machine_config_server_backend
backend ocp_machine_config_server_backend
mode tcp
balance source
server ocp-bootstrap 192.168.22.200:22623 check
server ocp-cp-1 192.168.22.201:22623 check
server ocp-cp-2 192.168.22.202:22623 check
server ocp-cp-3 192.168.22.203:22623 check
OCP Ingress - layer 4 tcp mode for each. Ingress Controller will handle layer 7.
frontend ocp_http_ingress_frontend
bind *:80
default_backend ocp_http_ingress_backend
mode tcp
backend ocp_http_ingress_backend
mode tcp
balance source
server ocp-w-1 192.168.22.211:80 check
server ocp-w-2 192.168.22.212:80 check
server ocp-w-3 192.168.22.213:80 check
server ocp-w-4 192.168.22.214:80 check
frontend ocp_https_ingress_frontend
bind *:443
default_backend ocp_https_ingress_backend
mode tcp
backend ocp_https_ingress_backend
mode tcp
balance source
server ocp-w-1 192.168.22.211:443 check
server ocp-w-2 192.168.22.212:443 check
server ocp-w-3 192.168.22.213:443 check
server ocp-w-4 192.168.22.214:443 check
[root@ocp-svc ocp-install]#
