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

[FeatureRequest] Allow for more than one TLSCertificateRef #6719

Open
modzilla99 opened this issue Oct 20, 2024 · 1 comment
Open

[FeatureRequest] Allow for more than one TLSCertificateRef #6719

modzilla99 opened this issue Oct 20, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor.

Comments

@modzilla99
Copy link

modzilla99 commented Oct 20, 2024

Hey there,

Right now it is only possible for the gateway.spec.listener.tls.certificateRefs to only contain one certificate. This in my opinion is very limiting as I have 3 domains + many subdomains that all need their own certificate. Since I don't want to manage them at all, I'd like to reference them in there so I do not have to specify the certificate in the TLS route as my users don't know what the name of the secret is.

@modzilla99 modzilla99 added kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. labels Oct 20, 2024
Copy link

Hey @modzilla99! Thanks for opening your first issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on Contour. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor.
Projects
None yet
Development

No branches or pull requests

1 participant