Fix service account token projected volume validation

[Taction]

What type of PR is this?

Add one of the following kinds:
/kind bug

What this PR does / why we need it:

Service account token projected volume validation should call validateLocalNonReservedPath on the token path.

Which issue(s) this PR fixes:

Fixes #121415

Does this PR introduce a user-facing change?

NONE

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

NONE

[k8s-ci-robot]

Welcome @Taction!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Taction. 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.

[Taction]

/sig auth

[liggitt]

/lgtm
/approve
/ok-to-test
/milestone v1.30

[Taction]

/test pull-kubernetes-e2e-kind

[liggitt]

/retest

[Taction]

Hello, I'm new here. It would take me some more time to figure out why e2e tests failed. Besides, who can help point out how to run k8s e2e tests locally or how to inspect what is wrong in the tests, any help would be appreciated.

[liggitt]

/lgtm cancel
/approve cancel

fix the nil check and squash down the change to a single commit, thanks

[ibihim]

/triage accepted

[Taction]

@liggitt Thank you so much for the advice, it works!

[liggitt]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: a4ce8d6995ed4d6b7726b9336a15dee430f0f771

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, Taction

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/api/OWNERS [liggitt]
• pkg/apis/OWNERS [liggitt]

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