[WinProxy] Adding additional validations to queried endpoint list iteration.

[princepereira]

What type of PR is this?

/kind cleanup
/kind regression

What this PR does / why we need it:

This PR adds additional validation to check if the endpoints queried from the nodes are with IpConfigurations.

Which issue(s) this PR fixes:

If the queried endpoints are with out any IpConfigurations, then it will end up in index out of bound exceptions which can create continuous crashing of kubeproxy.

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Fix 1.25 regression in WinProxy sync to handle queried endpoints without any IpConfigurations

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/sig windows
/sig network
/test pull-kubernetes-e2e-capz-windows-containerd-1-24

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines 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.

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.

[k8s-ci-robot]

Hi @princepereira. 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/test-infra repository.

[k8s-ci-robot]

@princepereira: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

…ration.

What type of PR is this?

/kind cleanup
/kind regression

What this PR does / why we need it:

This PR adds additional validation to check if the endpoints queried from the nodes are with IpConfigurations.

Which issue(s) this PR fixes:

If the queried endpoints are with out any IpConfigurations, then it will end up in index out of bound exceptions which can create continuous crashing of kubeproxy.

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

This PR adds additional validation for endpoint ip configuration while iterating through queried endpoint list.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/sig windows
/sig network
/test pull-kubernetes-e2e-capz-windows-containerd-1-24

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.

[sbangari]

/ok-to-test

[sbangari]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: princepereira, sbangari

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:

• pkg/proxy/winkernel/OWNERS [sbangari]

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

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 1318d0a7998efa1fb4021ffb5ab173133551c667