Configuring ingress cluster traffic using a load balancer

    If you do not need a specific external IP address, you can configure a load balancer service to allow external access to an OKD cluster.

    A load balancer service allocates a unique IP. The load balancer has a single edge router IP, which can be a virtual IP (VIP), but is still a single machine for initial load balancing.

    Before starting the following procedures, the administrator must:

    • Set up the external port to the cluster networking environment so that requests can reach the cluster.

    • Make sure there is at least one user with cluster admin role. To add this role to a user, run the following command:

    • Have an OKD cluster with at least one master and at least one node and a system outside the cluster that has network access to the cluster. This procedure assumes that the external system is on the same subnet as the cluster. The additional networking required for external systems on a different subnet is out-of-scope for this topic.

    If the project and service that you want to expose do not exist, first create the project, then the service.

    If the project and service already exist, skip to the procedure on exposing the service to create a route.

    Prerequisites

    • Install the CLI and log in as a cluster administrator.

    Procedure

    1. Create a new project for your service:

      1. $ oc new-project <project_name>

      For example:

      1. $ oc new-project myproject
    2. Use the oc new-app command to create a service. For example:

      1. $ oc new-app \
      2. -e MYSQL_USER=admin \
      3. -e MYSQL_PASSWORD=redhat \
      4. -e MYSQL_DATABASE=mysqldb \
      5. registry.redhat.io/rhscl/mysql-80-rhel7
    3. Run the following command to see that the new service is created:

      1. $ oc get svc -n myproject
      1. NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
      2. mysql-80-rhel7 ClusterIP 172.30.63.31 <none> 3306/TCP 4m55s

      By default, the new service does not have an external IP address.

    You can expose the service as a route by using the oc expose command.

    Procedure

    To expose the service:

    1. Log in to OKD.

    2. Run the following command to expose the route:

      1. $ oc expose service <service_name>

      For example:

      Example output

      1. route "mysql-80-rhel7" exposed
    3. Use a tool, such as cURL, to make sure you can reach the service using the cluster IP address for the service:

      1. $ curl <pod_ip>:<port>

      For example:

      1. $ curl 172.30.131.89:3306

      The examples in this section uses a MySQL service, which requires a client application. If you get a string of characters with the message, you are connected to the service.

      If you have a MySQL client, log in with the standard CLI command:

      1. $ mysql -h 172.30.131.89 -u admin -p

      Example output

      1. Enter password:
      2. Welcome to the MariaDB monitor. Commands end with ; or \g.
      3. MySQL [(none)]>

    Use the following procedure to create a load balancer service.

    Prerequisites

    • Make sure that the project and service you want to expose exist.

    To create a load balancer service:

    1. Log in to OKD.

    2. Load the project where the service you want to expose is located.

      1. $ oc project project1
    3. Open a text file on the control plane node (also known as the master node) and paste the following text, editing the file as needed:

      Sample load balancer configuration file

      1. apiVersion: v1
      2. kind: Service
      3. metadata:
      4. name: egress-2 (1)
      5. spec:
      6. ports:
      7. port: 3306 (2)
      8. loadBalancerIP:
      9. loadBalancerSourceRanges: (3)
      10. - 10.0.0.0/8
      11. type: LoadBalancer (4)
      12. selector:
      13. name: mysql (5)
    4. Save and exit the file.

    5. Run the following command to create the service:

      For example:

      1. $ oc create -f mysql-lb.yaml
    6. Execute the following command to view the new service:

      1. $ oc get svc

      Example output

      1. NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
      2. egress-2 LoadBalancer 172.30.22.226 ad42f5d8b303045-487804948.example.com 3306:30357/TCP 15m

      The service has an external IP address automatically assigned if there is a cloud provider enabled.

    7. On the master, use a tool, such as cURL, to make sure you can reach the service using the public IP address:

      1. $ curl <public-ip>:<port>

      For example:

      1. $ curl 172.29.121.74:3306

      The examples in this section use a MySQL service, which requires a client application. If you get a string of characters with the Got packets out of order message, you are connecting with the service:

      If you have a MySQL client, log in with the standard CLI command:

      1. $ mysql -h 172.30.131.89 -u admin -p
      1. Enter password:
      2. Welcome to the MariaDB monitor. Commands end with ; or \g.