-
Notifications
You must be signed in to change notification settings - Fork 566
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
Upgrade to k8s.io/kubernetes v1.22.1 #671
Upgrade to k8s.io/kubernetes v1.22.1 #671
Conversation
Hi @Ashley-wenyizha. 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/test-infra repository. |
/ok-to-test |
try go md vendor after go mod tidy? not sure the meaninig of
|
thanks for giving ok to test! here is what I did, added
|
4993f9b
to
e96e7e5
Compare
e96e7e5
to
e1da841
Compare
e1da841
to
7256eac
Compare
… names ignored issue
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Ashley-wenyizha, wongma7 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 |
Is this a bug fix or adding new feature?
Security patch for high Sev CVEs
What is this PR about? / Why do we need it?
k8s.io/kubernetes v1.20.11
--build_flags=--mod=mod
tohack/update-gomock
to work around build fail (not sure if this is recommended, let me know if there are better mitigations)What testing is done?
After this update, all the high risks and some medium risks from AWS enhanced ECR scanning is gone