Chores: Migrate deprecated wait.Poll* to context-aware equivalents.

[oyiz-michael]

What this PR does / why we need it

Migrate all deprecated wait.Poll* usages to context-aware equivalents to remove deprecation warnings and align with current client-go patterns (maintenance scope per #13002). This improves timeout/cancellation handling and future-proofs the codebase without changing behavior.

Changes

• wait.PollUntil → wait.PollUntilContextCancel
• wait.Poll / wait.PollImmediate → wait.PollUntilContextTimeout
• wait.ErrWaitTimeout checks → ctx.Err() == context.DeadlineExceeded
• Thread contexts/timeouts consistently through polling call sites

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

N/A — proactive maintenance/refactor aligned with project status (#13002).

How Has This Been Tested?

• go test ./... — all unit tests pass
• Verified e2e polling paths compile and respect context timeouts/cancellation
• Confirmed no behavioral changes: same polling intervals and exit conditions

Example migration

Before (deprecated):

err := wait.PollImmediate(1*time.Second, timeout, func() (bool, error) {
// ...
})
if err == wait.ErrWaitTimeout {
// handle timeout
}

After (context-aware):

ctx, cancel := context.WithTimeout(context.Background(), timeout)
defer cancel()

err := wait.PollUntilContextTimeout(ctx, 1*time.Second, timeout, true, func(ctx context.Context) (bool, error) {
// ...
})
if ctx.Err() == context.DeadlineExceeded {
// handle timeout
}

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added unit and/or e2e tests to cover my changes.
• All new and existing tests passed.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

Name	Link
🔨 Latest commit	7f53629
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-ingress-nginx/deploys/68a0c71a82b7ac00085ebb0e

[k8s-ci-robot]

Hi @oyiz-michael. 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.

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-sigs/prow repository.

[Gacko]

/triage accepted
/kind cleanup
/priority backlog
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gacko, oyiz-michael

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:

• OWNERS [Gacko]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Gacko]

/cherry-pick release-1.13

[Gacko]

/cherry-pick release-1.12

[k8s-infra-cherrypick-robot]

@Gacko: once the present PR merges, I will cherry-pick it on top of release-1.13 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.13

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@Gacko: once the present PR merges, I will cherry-pick it on top of release-1.12 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.12

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-sigs/prow repository.

[Gacko]

/ok-to-test

[k8s-infra-cherrypick-robot]

@Gacko: new pull request created: #13781

In response to this:

/cherry-pick release-1.13

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-sigs/prow repository.

[k8s-infra-cherrypick-robot]

@Gacko: new pull request created: #13782

In response to this:

/cherry-pick release-1.12

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-sigs/prow repository.

[oyiz-michael]

/assign