<p>I've been using Kubernete's <code>LoadBalancer</code> type service for incoming traffic on AWS. However, it is hard to terminate SSL at a service level, thus the idea of using an Ingress.</p>

<p>However, a <code>LoadBalancer</code> service allows us to make as many rolling changes as we like to our deployments without having to configure our DNS. By using Ingress, you can only use <code>NodePort</code> and while we would like to use Ingress, mapping DNS to new node when the pod is deployed on another node is a problem.</p>

<p>Is there a way to point a Kubernetes to point to an Ingress controller or use a service type <code>LoadBalancer</code> with an Ingress controller to terminate SSL.</p>

<p>We do not want to put our SSL certificates in a container, which is why this trouble.</p>

<blockquote>
  <p>Is there a way to point a Kubernetes to point to an Ingress controller or use a service type LoadBalancer with an Ingress controller to terminate SSL.</p>
</blockquote>

<p>You can simply deploy the on metal (nginx, haproxy, traefic...) ingress controllers as a pod/daemonset/rc in your cluster, and front it with a service of type=loadbalancer. You can find these controllers in various places like: <a href="https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx" rel="nofollow">https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx</a>, <a href="https://libraries.io/go/github.com%2Ftimelinelabs%2Fromulus" rel="nofollow">https://libraries.io/go/github.com%2Ftimelinelabs%2Fromulus</a>, <a href="https://github.com/containous/traefik/blob/fa25c8ef221d89719bd0c491b66bbf54e3d40438/docs/toml.md#kubernetes-ingress-backend" rel="nofollow">https://github.com/containous/traefik/blob/fa25c8ef221d89719bd0c491b66bbf54e3d40438/docs/toml.md#kubernetes-ingress-backend</a>, </p>
