Deploying the ingress controller for OpenShift or Kubernetes

The ingress controller is a load balancer for Kubernetes environments.

Related topics

Perform the following steps to install the ingress controller:

Download controller-nginx-ingress-controller:nginx-0.32. You can download it by using the attached ingress.yaml file.
If you change the ingress configuration and decide not to use the attached ingress.yaml file, make sure that the INGRESS_CLASS value in the configs/infra.config file matches the class in your ingress definition.

Create a secret from the trusted certificate and key. Depending on your cluster, run the following command:
OpenShift:

oc create secret tls my-tls-secret --cert=/path/to/cert.pem --key=/path/to/privkey.pem -n default

Kubernetes:

kubectl create secret tls my-tls-secret --cert=/path/to/cert.pem --key=/path/to/privkey.pem -n default

In the ingress-controller, do the following
1. In the args section, set the default certificate to my-tls-secret.
2. Set the ingress-class to knginx.
Ensure that you set the ingress class to knginx in the configs/infra.config file as shown below:
INGRESS_CLASS=knginx
(OpenShift) Create the Security Context Constraint (SCC). Run the following command;
```
oc create -f ingress-scc.yaml
```

Create a namespace and an ingress controller. Run the following commands in the given order:
OpenShift

1- oc new-project internet-ingress
2- oc create -f ingress.yaml

Kubernetes

1- kuebctl create ns internet-ingress
2- kubectl create -f ingress.yaml

For OpenShift clusters, add the ADM policy. Run the following command:

oc adm policy add-scc-to-user ingress-scc -z internet-ingress-serviceaccount -n internet-ingress

Update the DNS records in the infra.config file. All parameters in the infra.config file must have a valid DNS entry. The following entries are required for the ingress controller:
- TMS: Value of the TMS_LB_HOST parameter
- RSSO: Value of the LB_HOST parameter
- Tenant: Derived from ENVIRONMENT, TENANT_TYPE, and DOMAIN parameters
- MinIO: Value of the MINIO_LB_HOST parameter
- Self-observability: Derived from ENVIRONMENT, TENANT_TYPE, and DOMAIN parameters. For example, $COMPANY_NAME-self-$TENANT_TYPE-$ENVIRONMENT$DOMAIN
- (Only for BMC Helix Operations Management) BMC Discovery Appliance: Derived from ENVIRONMENT, TENANT_TYPE, and DOMAIN parameters - $COMPANY_NAME-disc-$TENANT_TYPE-$ENVIRONMENT$DOMAIN
- (Only for BMC Helix Continuous Optimization) Derived from ENVIRONMENT, TENANT_TYPE, and DOMAIN parameters - $COMPANY_NAME-optimize-$TENANT_TYPE-$ENVIRONMENT$DOMAIN
  For example: acme-optimize-private-poc.acme.com
  For more information about the infra.config and deployment.config files, see Configuration file settings.
Edit or patch the external load balancer IP addresses that computers outside your local network use to connect to identify your network.
In a Kubernetes environment, pods are used as nonpermanent resources whose IP addresses keep on changing. External IPs are required for the frontends to keep track of the pods.
For information about the external IP format, see the Kubernetes documentation .
Run the following command:
OpenShift
```
oc edit svc internet-ingress -n internet-ingress
```
Kubernetes
```
kubectl edit svc internet-ingress -n internet-ingress
```
Delete the ingress controller pods.
Verify that the URL shows a secured connection.

Configure the load balancer.
Add the ports for the following:

The load balancer input port (443)
The load balancer output nodes, which are the worker nodes

The external ports for the load balancer output nodes. Obtain these nodes from the ingress controller. Use the following command, where port 31301 is configured that maps to the Kubernetes internal port 443:

>kubectl get service  | head -1
NAMESPACE                                          NAME                                                              TYPE           CLUSTER-IP       EXTERNAL-IP                            PORT(S)                                           AGE

>kubectl get service -A | grep internet-ingress | grep LoadBalancer
internet-ingress                                   internet-ingress                                                  LoadBalancer   172.30.242.1     172.25.146.75                          443:31391/TCP,80:30888/TCP                        9d

Deploying the ingress controller for OpenShift or Kubernetes

Comments