Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Enhancement] Support configuring the TLS Secret on Ingress listener to enable cert-manager support for issuing certificates
See original GitHub issueIs your feature request related to a problem? Please describe.
Currently when using the Kubernetes Ingress external listener with Nginx Ingress controller, there is no way to specify a TLS secretName, which would allow cert-manager, for example, to issue certificates for the Ingress resources.
Describe the solution you’d like
When using the Kubernetes Ingress external listener with Nginx Ingress controller, I would like the ability to use cert-manager to issue certificates for the created Ingress resources. To do this I would require a way to configure two properties:
- add annotations like
cert-manager.io/issueretc. - specify a
secretName
The first property is configurable using dnsAnnotations, however, there doesn’t seem to be an option to specify the secretName currently.
If the secretName could be specified, it would allow certificates to be issued by cert-manager for the created Ingress resources.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, correct.
As described in https://strimzi.io/blog/2021/05/07/deploying-kafka-with-lets-encrypt-certificates/, this should now be possible, although in slightly different way (the certificates need to be set in Kafka and not in Ingress due to the TLS passthrough). I think this can be closed.