Nginx Ingress Controller not enabling TLS/HTTPS

[wernight]

Following https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx/examples/tls and other examples there I my Nginx Ingress works on HTTP but refuses to connect on port 443 even when I'm directly on that Pod. The generated nginx.conf does not contain any 443, and my Ingress definition worked on GCE Ingress.

Another strange thing is that https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx/examples/tls describes the standard tls.key and tls.crt (also used by GCE Ingress) but then https://github.com/kubernetes/contrib/blob/master/ingress/controllers/nginx/examples/tls/dhparam.sh generates a dhparam.pem and I also get a matching warning from Nginx Ingress Controller:

ssl.go:132] no file dhparam.pem found in secrets

Possibly related to #1525

[wernight]

Looking at https://github.com/kubernetes/contrib/blob/53cc5309d8228c9b3f3d06c5db02cce06ef8e43a/ingress/controllers/nginx/controller.go#L869 I found a matching error Secret default/ does not exists, which means it's looking for a secret named default/ (or actually empty in namespace default).

The reason was a wrong Ingress (with extra -):

spec:
  tls:
    - secretName: tls-certificate
    - hosts:
        - foo.com

May be a better error for Secret %v does not exists would be helpful.

[fejta-bot]

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close