haproxy-ingress
haproxy-ingress copied to clipboard
jcmoraisjr
Allow custom secret keys in kubernetes secret instead of hardcoded tls.crt and tls.key secret keys
What are you trying to do
I am trying to implement SSL in haproxy. We have a in-house cert mgmt utility that can create a x509 cert and rotate based on TTL. this utility creates a secret in app namespace with default keys like certs and privatekey secret keys. We are trying to get haproxy use those keys, instead of us manually creating another secret that suites haproxy.
What HAProxy Ingress should do or how it should behave differently
currently the haproxy certificate secret keys are hardcoded to tls.cert and tls.key, could you please provide flexibility to allow custom secret key names? Appreciate your help in this regards.
@jcmoraisjr just checking out to see if we are going to see this in an upcoming release. Thank you!!
@jcmoraisjr any rough estimate on implementation? I hope to see this feature.
Hi, so many pretty good new features still in the roadmap and zero time to make it happen, sorry. I'm currently with some other parallel activities stealing time from coding this ingress, and I still need to finish gateway api support. I hope that I can start with new implementations after moving v0.15 to beta, hopefully by the end of this year.