Closed HusainZafar closed 1 year ago
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.
Hi @HusainZafar. 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 /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test
/approve
in other words, this is cherry-pick of https://github.com/kubernetes/cloud-provider-aws/pull/565 on to 1.26 branch :+1:
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nckturner, wongma7
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/release-note-none
What type of PR is this?
/kind feature
What this PR does / why we need it: This adds the fargate IPV6 patch on top of the v1.26.6 release. The patch is available in 1.27 and 1.28 but missing in 1.26
Which issue(s) this PR fixes:
NONE
Special notes for your reviewer: Request the repo owners to please create a new tag v1.26.7 since I do not have the permissions
Does this PR introduce a user-facing change?:
NONE