-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🐛 Also use tls options for metrics/diagnostics server #10883
Conversation
Welcome @awprice! |
Hi @awprice. Thanks for your PR. I'm waiting for a kubernetes-sigs 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-sigs/prow repository. |
/area security |
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.
/lgtm
LGTM label has been added. Git tree hash: 48b9cfc8e4a3541b710b694942b1269ca020e36d
|
/ok-to-test |
/lgtm |
@neolit123 Thx for the review! I think I addressed all findings, PTAL :) |
/test pull-cluster-api-e2e-conformance-ci-latest-main |
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.
thanks
/lgtm
/approve
/hold
please drop the hold if no more review is needed.
LGTM label has been added. Git tree hash: 60b845b6781bd163506fd750b2e21b064f5a8c95
|
Seems very unrelated /test pull-cluster-api-e2e-main |
"Preferred values: "+strings.Join(tlsCipherPreferredValues, ", ")+". \n"+ | ||
"Insecure values: "+strings.Join(tlsCipherInsecureValues, ", ")+".") | ||
|
||
fs.StringVar(&options.MetricsBindAddr, "metrics-bind-addr", "", |
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.
q: when can we actually remove this? (might be worth adding a comment)
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.
Good question. I'm not sure. I was even thinking about just dropping it, but it's too close to the release now.
Not sure if we should hard-code a release here, but maybe let's drop it for the next release? (fine for me to decide this now and update the description to reflect that)
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.
Also, slightly unrelated, but should we document the change on flags utils in the upgrade doc?
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.
Let's open an issue for removal of the flag in the next release (so it is tracked)
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.
/lgtm |
Signed-off-by: Alex Price <aprice@atlassian.com>
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.
/lgtm
/approve
LGTM label has been added. Git tree hash: f17197d43206596c9828b915cf982526cd0b7644
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, neolit123 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The flake that I got on the e2e-main job also occurs on other PRs and on the main branch. Will triage / fix independently |
/hold cancel |
@awprice: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
What this PR does / why we need it:
Passes the TLS options flags to the diagnostics server so that it receives the same TLS options as the webhook endpoint
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #10882