Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
What would you like to be added: I would like to see some mechanism built in to Kubernetes to be able to support the use of TLS Certificates / Secrets that have been created on a windows machine and therefore contain windows line ending characters.
Why is this needed: I have found when developing many kubernetes based applications over the past few years, that make use of an ingress and tls certificates, a very common issue that comes up is when an ingress TLS certificate is created and used in the likes of an NGINX Ingress Controller. If that TLS certificate was created on some machine such as Windows, that introduced windows line endings as opposed to Unix line endings, anything that uses those like an Ingress would not work correctly and give certificate validation errors. One workaround has been to ask that 'dos2unix' is run on the certificates before creating them as secrets. Is this something that we think could be handled within Kubernetes itself so that this common troubleshooting step is not required.
@mark007: Reiterating the mentions to trigger a notification: