Experiment with NGINX Ingress Controller

AWS load balancers are surprisingly expensive—on the order of $16 per month, plus traffic/compute charges. If we consistently use `LoadBalancer` service types for whichever applications we wish to expose from a Kubernetes cluster, the LB charges will stack up quickly. A possible alternative may be provided by the NGINX ingress controller. It will take some investigation to determine if this can fill this need, but preliminary investigations suggest that it may be possible to use it to handle k8s `Ingress`es, providing a route for each ingress, with only the NGINX service requiring an AWS-provided load balancer, thereby multiplexing that LB across many applications.

This issue covers the investigation into whether this setup is possible, and also to test and document its use for future projects. If successful, subsequent issues can be created to move any deployed applications to this method.

Start by reviewing the repository's current Kubernetes service exposure and compare LoadBalancer services with the NGINX Ingress Controller and Kubernetes Ingress resources. Test whether one AWS load balancer can route multiple applications, then document the setup, findings, and limitations for future projects.

Written by the indexing model from the issue text.