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
Update webhook test code to golang 1.21 #118156
Update webhook test code to golang 1.21 #118156
Conversation
Hi @HirazawaUi. 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. |
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: 955bad30ef1c27a25ff3caee0ceb3167901485d5
|
/lgtm |
/ok-to-test |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: HirazawaUi, liggitt, pacoxu 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 |
@HirazawaUi could you cherry-pick this PR to old branches v1.24-v1.27? |
Ok, I will do this |
/triage accepted |
…118156-upstream-release-1.27 Automated cherry pick of #118156: update webhook test to go 1.21
…118156-upstream-release-1.26 Automated cherry pick of #118156: update webhook test to go 1.21
…118156-upstream-release-1.25 Automated cherry pick of #118156: update webhook test to go 1.21
…118156-upstream-release-1.24 Automated cherry pick of #118156: update webhook test to go 1.21
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
In Go 1.21, TLS bad certificate errors become more specific and can cause tests to fail
Which issue(s) this PR fixes:
Fixes #118153
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: