change snapshot controller image version to 6.2.1 in release-6.2 branch#811
change snapshot controller image version to 6.2.1 in release-6.2 branch#811Jainbrt wants to merge 2 commits intokubernetes-csi:release-6.2from Jainbrt:release-6.2
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Jainbrt The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @Jainbrt. Thanks for your PR. I'm waiting for a kubernetes-csi 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. DetailsInstructions 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. |
|
@xing-yang would you be able to help to get through the trivy scanner failure ? |
|
/retest |
|
@Jainbrt: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
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. |
|
We'll have to submit a PR to resolve the CVEs in order to pass the Trivy scanner. This lib golang.org/x/net needs to be updated to a newer version. |
|
/ok-to-test |
|
Thanks @xing-yang for responding. would you suggest to raise a new PR for CVEs? |
@Jainbrt Yes, can you help raise a separate PR to fix the CVEs? |
Created a PR for this #815. |
|
/retest |
|
You probably need to do a rebase. |
|
Can you squash your commits? |
Signed-off-by: Abhishek Jain <abjain39@in.ibm.com>
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: