Skip to content
New issue

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

Specify existing secret names for Ingress HTTPS certs #490

Open
hardillb opened this issue Nov 1, 2024 · 0 comments
Open

Specify existing secret names for Ingress HTTPS certs #490

hardillb opened this issue Nov 1, 2024 · 0 comments
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do

Comments

@hardillb
Copy link
Contributor

hardillb commented Nov 1, 2024

Description

This will allow users to provision certs manually (e.g. wildcards) when TLS not handled by certificate manager or LoadBalancer TLS termination.

Requested By

  • Customer name and/or link to HubSpot contact
@hardillb hardillb added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do labels Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do
Projects
Status: No status
Development

No branches or pull requests

1 participant