-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Ignore default certificate during server initialization #4563
Conversation
Hi @zeeZ. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: zeeZ The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@zeeZ please add e2e tests |
// only add a certificate if the server does not have one previously configured | ||
if servers[host].SSLCert != nil { | ||
// only add a certificate if the server does not have one previously configured that is not the default | ||
if servers[host].SSLCert != nil && servers[host].SSLCert.PemFileName != n.cfg.DefaultSSLCertificate && servers[host].SSLCert != n.cfg.FakeCertificate { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just checked against the current master and you're absolutely correct, the behavior changed since the last release!
This pull request's desired behavior is in master, so I'm closing this. I might tackle those e2e tests when I have more time to figure them out in the future- |
What this PR does / why we need it: Recreation of #2279. When the oldest Ingress for a domain contains a TLS section, but no secret, the default certificate will always be used, even though a newer Ingress may contain a valid secret.
This PR tries to change the behavior from ignoring all further certificates if any certificate is present to ignoring all further certificates if any non-default certificate is present
Special notes for your reviewer: See the old PR for examples