Adding a nil check in endpointslicecache

[robscott]

What type of PR is this?
/kind bug

What this PR does / why we need it:
The only way I've been able to cause this to be nil here is with a test where I unintentionally wasn't initializing endpointslicecache properly, but this seemed like a place that would be better and safer with a nil check, so here it is.

Which issue(s) this PR fixes:
There's a tiny chance this could help with #82174, though all my e2e testing today suggests that will already be fixed when #82380 gets in.

Does this PR introduce a user-facing change?:

NONE

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

• KEP
• Enhancement Issue

/milestone 1.16
/cc @bowei @lachie83

[k8s-ci-robot]

@robscott: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

What type of PR is this?
/kind bug

What this PR does / why we need it:
The only way I've been able to cause this to be nil here is with a test where I unintentionally wasn't initializing endpointslicecache properly, but this seemed like a place that would be better and safer with a nil check, so here it is.

Which issue(s) this PR fixes:
There's a tiny chance this could help with #82174, though all my e2e testing today suggests that will already be fixed when #82380 gets in.

Does this PR introduce a user-facing change?:

NONE

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

• KEP
• Enhancement Issue

/milestone 1.16
/cc @bowei @lachie83

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 @robscott. 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.

[bowei]

/ok-to-test

[bowei]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bowei, robscott

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/OWNERS [bowei]

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

[dims]

/milestone v1.16

re-apply the milestone as it was not applied (see PR text)

[k8s-ci-robot]

@dims: The provided milestone is not valid for this repository. Milestones in this repository: [next-candidate, v1.13, v1.14, v1.15, v1.16, v1.17, v1.18, v1.19]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 1.16

re-apply the milestone as it was not applied (see PR text)

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.

[dims]

/priority important-soon

[dims]

/milestone v1.16