-
Notifications
You must be signed in to change notification settings - Fork 190
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
chore: Update dependencies cloud provider azure #1662
chore: Update dependencies cloud provider azure #1662
Conversation
Welcome @cvvz! |
Hi @cvvz. 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. |
7f6a81b
to
13a9fae
Compare
/ok-to-test |
3f1da21
to
1c1bb2d
Compare
/retest |
4 similar comments
/retest |
/retest |
/retest |
/retest |
55821b6
to
e306d38
Compare
/test pull-azuredisk-csi-driver-e2e-capz |
/retest |
5d01b8c
to
5967801
Compare
boilerplate fix ut use go1.19 Revert "use go1.19" This reverts commit a8cb5db. test: fix trivy action test: fix golint error fix: golint error test: fix golint error test: fix golint test: fix golint test: fix golint test: fix golint use ginkgo v2 use latest mount-utils fix e2e fake mounter set framework namespace podSecurity enforcelevel to privileged fix verify add ginkgo.timeout fix
5967801
to
115c46e
Compare
/retest |
1 similar comment
/retest |
/retest |
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
thanks, actually I mean it could be squashed to fewer commits, e.g. vendor change, e2e test fix, windows interface fix, etc. That would be more clear, it's not necessary always to be one commit in one PR.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx, cvvz 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 |
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Requirements:
Special notes for your reviewer:
Release note: