Configuring a webserver or loadbalancer is harder than it should be. Most webserver configuration files are very similar. There are some applications that have weird little quirks that tend to throw a wrench in things, but for the most part you can apply the same logic to them and achieve a desired result.
The Kubernetes Ingress resource embodies this idea, and an Ingress controller is meant to handle all the quirks associated with a specific “class” of Ingress.
The NGINX Ingress Controller is built around the Kubernetes Ingress resource, using a ConfigMap to store the NGINX configuration.
The NGINX Ingress Controller is a daemon, deployed as a Kubernetes Pod, that watches the apiserver’s /ingresses endpoint for updates to the Ingress resource. Its job is to satisfy requests for Ingresses.
How to Connect to Your Cluster
Follow these instructions to connect to your cluster with
doctl. Additional instructions for connecting to your cluster are included in the DigitalOcean Control Panel.
You may also connect to your cluster without using
doctl if you have taken the following prerequisite steps:
1- Created a cluster in the DigitalOcean Control Panel.
2- Downloaded the Kubernetes config file to ~/Downloads directory on your local machine. The config file will have a name like
3- Installed the Kubernetes command line tool,
kubectl, on your local machine. (Here are instructions for doing that) if you have not already done so.