Ingress tries to create SSL certificate from secret with illegal name

[rgfunk]

With revision acbecb5 the naming for SSL certificates created from secrets was changed to include the ingress-uid as a suffix (in namer.go). However, clusters with ingress resources created before kubernetes version 1.3 have an empty ingress-uid, as described here:

https://github.com/kubernetes/ingress-gce/blob/master/BETA_LIMITATIONS.md#changing-the-cluster-uid

This leads to an illegal name for the ssl certificate (ending in "--"). Setting the uid is not an option as this would require deleting all ingress resources, which is currently not possible. It would be great if the naming supported a fallback in case the ingress-uid is not set.

The creation of all other ingress resources works fine without having the ingress-uid set.

[bowei]

/assign @prameshj

[k8s-ci-robot]

@bowei: GitHub didn't allow me to assign the following users: prameshj.

Note that only kubernetes members and repo collaborators can be assigned.

In response to this:

/assign @prameshj

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[prameshj]

I'll work on a fix for this.