Configuring the Informix NodePort with an Ingress controller

If you use an external infrastructure node to route external Informix traffic into the Red Hat® OpenShift® cluster, the cluster might be in a private zone and you need to configure an external-facing Ingress controller to route the traffic to the OpenShift nodes.

About this task

Because Informix is externally exposed through a NodePort, the Ingress controller also needs to expose the NodePort in order to allow traffic into the cluster.

The configuration below is only applicable with an HAProxy Ingress controller. For more detail about configuring networking, see Understanding networking in the OpenShift documentation.

Procedure

  1. On the infrastructure node, open the HAProxy configuration file located at /etc/haproxy/haproxy.cfg.
  2. Modify the haproxy.cfg file to include the OpenShift NodePort you want to expose: 
    frontend informix
        bind *:informix NodePort
        default_backend informix_be
        mode tcp
        option tcplog
backend informix_be
        balance source
        mode tcp
        server master0 Master0-privateIP:Informix NodePort check
        server master1 Master1-privateIP:Informix NodePort check
        server master2 Master3-privateIP:Informix NodePort check
  3. Reload HAProxy: 
    systemctl reload haproxy