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

Create a new project for your service by running the oc new-project command:
```
$ oc new-project myproject
```

Use the oc new-app command to create your service:

$ oc new-app nodejs:12~https://github.com/sclorg/nodejs-ex.git

To verify that the service was created, run the following command:

$ oc get svc -n myproject

NAME        TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
nodejs-ex   ClusterIP   172.30.197.157   <none>        8080/TCP   70s

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:

Log in to OKD.
Log in to the project where the service you want to expose is located:
```
$ oc project myproject
```
To verify that the service is exposed, you can use a tool, such as cURL, to make sure the service is accessible from outside the cluster.
1. Use the oc get route command to find the route’s host name:
```
$ oc get route
```
  Example output
```
NAME        HOST/PORT                        PATH   SERVICES    PORT       TERMINATION   WILDCARD
```
2. Use cURL to check that the host responds to a GET request:
```
$ curl --head nodejs-ex-myproject.example.com
```
  Example output
```
HTTP/1.1 200 OK
...
```

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:

Log in to OKD.
Load the project where the service you want to expose is located.
```
$ oc project project1
```

Open a text file on the control plane node and paste the following text, editing the file as needed:

Sample load balancer configuration file

apiVersion: v1
kind: Service
metadata:
  name: egress-2 (1)
spec:
  - name: db
    port: 3306 (2)
  loadBalancerIP:
  loadBalancerSourceRanges: (3)
  - 192.168.0.0/16
  type: LoadBalancer (4)
  selector:
    name: mysql (5)

Save and exit the file.
Run the following command to create the service:

For example:
```
$ oc create -f mysql-lb.yaml
```

Execute the following command to view the new service:

$ oc get svc

Example output

NAME       TYPE           CLUSTER-IP      EXTERNAL-IP                             PORT(S)          AGE
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.

On the master, use a tool, such as cURL, to make sure you can reach the service using the public IP address:
```
$ curl <public-ip>:<port>
```
For example:
```
$ 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:
Example output