Closed kmala closed 11 months 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 @kmala. 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 /lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cartermckinnon, dims
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@kmala You willing to backport this to 1.25-1.23 as well? Those release branches are still maintained.
@kmala You willing to backport this to 1.25-1.23 as well? Those release branches are still maintained.
I didn't backport as updating otel dependencies has backward incompatible changes which needs changes in the kubernetes/kubernetes where these branches are not maintained
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
cherry pick of #741 and #740 on release-1.26
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: