title: Kubernetes nginx-ingress TLS issue
body: <p>My company has an existing CA certificate for <em>fake.example.com</em> and an A record that maps <em>fake.example.com</em> to the IP of our load balancer</p>
  
  <p>The load balancer is forwarding traffic to our Kubernetes cluster.</p>
  
  <p>In the cluster, I've deployed the nginx-ingress helm chart, exposing NodePort for https at 30200</p>
  
  <p>I've created a k8s TLS secret named <em>test-secret</em> from the above certificate.</p>
  
  <p>I've deployed an app with service 'test' and have installed the following ingress:</p>
  
  <pre><code>apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    name: test-ingress
    namespace: default
    annotations:
      kubernetes.io/ingress.class: nginx
  spec:
    tls:
    - hosts:
      - fake.example.com
      secretName: test-secret
    rules:
      - host: fake.example.com
        http:
          paths:
          - path: /myapp
            backend:
              serviceName: test
              servicePort: 8080
  </code></pre>
  
  <p>So, if i execute</p>
  
  <pre><code>curl https://{ip for k8s node}:30200/myapp/ping -H 'Host:fake.example.com' -k --verbose
  </code></pre>
  
  <p>I get the expected response from my app, but I also see</p>
  
  <pre><code>* Server certificate:
  *  subject: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
  *  start date: Jan 25 20:52:16 2018 GMT
  *  expire date: Jan 25 20:52:16 2019 GMT
  *  issuer: O=Acme Co; CN=Kubernetes Ingress Controller Fake Certificate
  </code></pre>
  
  <p>I've confirmed in the nginx.conf file that for <em>server_name fake.exampe.com</em> the <em>ssl_certificate</em>, <em>ssl_certificate_key</em> , and <em>ssl_trusted_certificate</em> are pointing the the correct location</p>
  
  <p>So my question is, is it possible to configure nginx to use the correct certificate in this scenario?</p>