• Comments
  • openshift OCP4: nodes ready in cluster, but loadBalancer haProxy ingress fails.

    Posted on

    with oc get node I can see all nodes.

    $ oc get nodes
    NAME                     STATUS   ROLES    AGE     VERSION
    master0.ocp4.robot.com   Ready    master   9d      v1.17.1+809da40
    master1.ocp4.robot.com   Ready    master   9d      v1.17.1+809da40
    master2.ocp4.robot.com   Ready    master   9d      v1.17.1+809da40
    worker0.ocp4.robot.com   Ready    worker   9d      v1.17.1+809da40
    worker1.ocp4.robot.com   Ready    worker   9d      v1.17.1+809da40
    worker2.ocp4.robot.com   Ready    worker   4d22h   v1.17.1+809da40
    *worker3.ocp4.robot.com*   Ready    worker   12h     v1.17.1+809da40
    (base) TPERIASA-M-33YP:~ tperiasa$ oc status
    In project default on server https://api.ocp4.robot.com:6443
    svc/openshift - kubernetes.default.svc.cluster.local
    svc/kubernetes - 172.30.0.1:443 -> 6443
    

    But worker3 is addeded recently and does not show up in loadbalancer haProxy ingress

    Not sure how to debug this issue
    haproxy configs:

    frontend ingress-https
        bind *:443
        default_backend ingress-https
        mode tcp
        option tcplog
    
    backend ingress-https
        balance source
        mode tcp
        server worker0.ocp4.robot.com worker0.ocp4.robot.com:443 check
        server worker1.ocp4.robot.com worker1.ocp4.robot.com:443 check
        server worker2.ocp4.robot.com worker2.ocp4.robot.com:443 check
        server worker3.ocp4.robot.com worker3.ocp4.robot.com:443 check
    

    is there a way to see ingress issues in openshift4.4 (ocp4.4.x).?

    by

    points

    Responses

    Red Hat
    © 2025 Red Hat, Inc.