<p>I'm trying to configure an elastic ip with Amazon's Elastic Kubernetes service so I can expose a static public IP address. So far it seems the only way to expose a static public IP address is through a load balancer which is kind of a waste since I have a static private IP address endpoint for the service but no way to expose it publicly. And I only need 1 instance of the service running since HA isn't a requirement here. I have tried everything I can think of even to manually configuring an elastic ip but it seems that if that is a solution, the steps are a little convoluted and seems odd that you would have to do such a thing. </p>

Josh Woodcock
<p>The only possible way with EKS is to use a Load Balancer. In our case, we needed to have a fixed CNAME to use in Route53. We ended up using a Load Balancer that points to our web server, that was set up as a Deployment.
As you mentioned I thought that using a Load Balancer was a waste because we only have 1 deployment, but it ended up to be quite helpful, especially because we configure the deployment to use a readinessProbe, in that way the Balancer switch to the Pod only when it's ready. 
The Load Balancer CNAME is then used as a RecordSet in Route53.</p>
