-
Notifications
You must be signed in to change notification settings - Fork 68
Supporting multiple TLS certs #120
Comments
Thanks for the issue and offering to help @kinghrothgar Yes kubemci does not support multiple TLS certs and as pointed out in the issue you linked, neither does the ingress-gce controller. I will recommend trying it manually first and verifying that it works. Create a multicluster ingress using kubemci and then update the target proxy to include links to multiple certs. Once we have verified that it works, we can update the code.
Eventually, we should add support to ingress-gce controller as well, and share more code with it. |
@kinghrothgar Were you able to try it out? Also is this issue blocking you? Wondering if you have been able to use kubemci without multiple TLS certs. Feel free to chime in on #117. |
I don't believe this is blocking me as once I've set up the LB I believe I can go in and add more TLS certs to the LB without messing anything up. I have not tested this yet. EDIT: We are still planning on working on this, I just have several weeks over other Kubernetes work to do before this is back on my sprint. |
Yes it should work fine as long as you dont run kubemci command again. |
cc @prameshj who is adding support for this in ingress-gce: kubernetes/ingress-gce#142. We still need to work on adding support for that in kubemci |
It seems this is now support by |
I confirm multiple TLS certs doesn't work as-is with ingress-gce does support multi-TLS, so we should improve kubemci. |
Actually, I just tried today and the additional certificates seem to remain intact after remove-clusters and create -f. |
As far as I can tell, this does not support having multiple TLS certs. My coworker @fastest963 and I are willing to put some time in to add support for this. I see there is some discussion on this topic here kubernetes/ingress-gce#46. Are there any known hurdles for this or any suggestions on getting started?
The text was updated successfully, but these errors were encountered: