Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

GLBC Ingress TLS - new secret did not get applied because of redundant "k8s-ssl-1*" cert #2521

Closed
bbzg opened this issue Apr 4, 2017 · 2 comments
Closed

GLBC Ingress TLS - new secret did not get applied because of redundant "k8s-ssl-1*" cert #2521

bbzg opened this issue Apr 4, 2017 · 2 comments

Comments

@bbzg
Copy link

bbzg commented Apr 4, 2017

Kubernetes 1.5.4 on GKE

Similar/same as #1396

After replacing the secret holding the TLS cert, nothing happened. Found #1396, that pointed me in the right direction - deleting the extra certificate that was not connected to any ingress. After doing that (about 5-10 minutes) the certificate was swapped out on the ingress and used.
@aledbf
Copy link
Contributor

aledbf commented Apr 6, 2017

@bbzg please open the issue in the new ingress repository https://github.com/kubernetes/ingress

@bbzg
Copy link
Author

bbzg commented Apr 15, 2017

kubernetes/ingress-nginx#609

@bbzg bbzg closed this as completed Apr 15, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aledbf @bbzg