We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The operator should allow for custom TLS certificates for Ingress. Currently, the expected secret name is the Ingress manifest's name + -tls-cert.
When using LetsEncrypt via Cert-Manager, the secrets are named however the user requests it to be.
I plan to:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Goal
The operator should allow for custom TLS certificates for Ingress.
Currently, the expected secret name is the Ingress manifest's name + -tls-cert.
When using LetsEncrypt via Cert-Manager, the secrets are named however the user requests it to be.
Actions steps
I plan to:
The text was updated successfully, but these errors were encountered: