Deploy NGINX Ingress Controller¶
In this section you will configure and deploy the NGINX Ingress Controller and expose it using a Classic Load Balancer.
Go to your GitOps repository, inside your
root@rok-tools:~# cd ~/ops/deployments
bases: #- ../ingress-alb - ../service-elb #- ../service-azurelb
rok/nginx-ingress-controller/overlays/deploy/kustomization.yamland enable only the
patches: #- path: patches/ingress-alb.yaml #- path: patches/service-alb.yaml - path: patches/service-elb.yaml #- path: patches/service-azurelb.yaml
rok/nginx-ingress-controller/overlays/deploy/patches/service-elb.yamland set the
aws-load-balancer-internalannotation. Choose one of the following options, based on the ELB scheme:
Enable the firewall in your Classic Load Balancer and allow access only to specific CIDRs. Choose one of the following options, based on your ELB scheme:
Commit your changes:
root@rok-tools:~/ops/deployments# git commit -am "Expose NGINX Ingress Controller with a Classic Load Balancer"
Deploy NGINX Ingress Controller:
root@rok-tools:~/ops/deployments# rok-deploy --apply rok/nginx-ingress-controller/overlays/deploy
Verify that NGINX Ingress Controller is up-and-running. Check pod status and verify field STATUS is Running and field READY is 1/1:
root@rok-tools:~/ops/deployments# kubectl -n ingress-nginx get pods NAME READY STATUS RESTARTS AGE nginx-ingress-controller-7f74f657bd-ln59l 1/1 Running 0 1m
Verify that the Load Balancer Service has an external IP:
root@rok-tools:~/ops/deployments# kubectl -n ingress-nginx get service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE ingress-nginx LoadBalancer 10.32.1.249 a4d794bfa6d7e440facc4398bf96edde-992601283.us-east-1.elb.amazonaws.com 80:30099/TCP,443:30719/TCP 1m
The Service object does not get an EXTERNAL-IP.
Describe the service:
root@rok-tools:~/ops/deployments# kubectl describe service -n ingress-nginx ingress-nginx
If you see an event like the following:
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning UnAvailableLoadBalancer 1m service-controller There are no available nodes for LoadBalancer
it means that your subnets are misconfigured.
Verify your subnets configuration.
You have successfully deployed the NGINX Ingress Controller, and exposed it using a Classic Load Balancer.