Closed cartermckinnon closed 1 year ago
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign m00nf1sh for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
This issue is currently awaiting triage.
If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
@cartermckinnon: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
pull-cloud-provider-aws-test | c95ff35e2573b12c72332837929cdb2a016af712 | link | true | /test pull-cloud-provider-aws-test |
pull-cloud-provider-aws-check | c95ff35e2573b12c72332837929cdb2a016af712 | link | true | /test pull-cloud-provider-aws-check |
pull-cloud-provider-aws-e2e | c95ff35e2573b12c72332837929cdb2a016af712 | link | true | /test pull-cloud-provider-aws-e2e |
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.
Oops, wrong base.
What type of PR is this? /kind cleanup
What this PR does / why we need it:
Preparing to cut a patch release, resolving some CVE's.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: NONE