Assign FQDN to MetalLB

In this section you will assign an FQDN to your MetalLB Load Balancer.

See also

• How to add extra DNS records on Bright clusters.

Fast Forward

If you have already assigned an FQDN for your serving domain to MetlLB Load Balancer, expand this box to fast-forward.

1. Proceed to the Verify section.

What You’ll Need

• A configured management environment.
• Your clone of the Arrikto GitOps repository.
• A working NGINX Ingress Controller deployment.

Procedure

1. Go to your GitOps repository, inside your rok-tools management environment:

   

   root@rok-toos:~/# cd ~/ops/deployments

2. Specify the FQDN to use for Serving:

   

   root@rok-tools:~/ops/deployments# export FQDN=<FQDN>

   Replace <FQDN> with your FQDN. For example:

   

   root@rok-tools:~/ops/deployments# export FQDN=serving.example.com

3. Obtain the IP address of your Load Balancer and print its value. Choose one of the following options based on which NGINX you are using:

   Serving NGINX

   EKF NGINX

   

   root@rok-tools:~# export ADDRESS=$(kubectl get services -n ingress-nginx-serving ingress-nginx \ > -o jsonpath={.status.loadBalancer.ingress[].ip}) && echo ${ADDRESS?} 10.0.0.2

   

   root@rok-tools:~# export ADDRESS=$(kubectl get services -n ingress-nginx ingress-nginx \ > -o jsonpath={.status.loadBalancer.ingress[].ip}) && echo ${ADDRESS?} 10.0.0.1

4. Create a DNS record in your nameservers, so that your FQDN resolves to the IP address of your Load Balancer.

Verify

1. Verify that your FQDN resolves to the IP of your Load Balancer:

   

   root@rok-tools:~/ops/deployments# host ${FQDN?} 10.0.0.2

Summary

You have successfully assigned an FQDN to your Load Balancer.

What’s Next

The next step is to deploy cert-manager.

• Deploy cert-manager