Fix typos in rbac api.

[zhanluxianshen]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Fix typos in rbac api.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

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

[linux-foundation-easycla]

• ✅login: zhanluxianshen / (609b01f)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Please note that we're already in Test Freeze for the release-1.30 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.30.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Thu Mar 28 20:12:24 UTC 2024.

[k8s-ci-robot]

Welcome @zhanluxianshen!

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 @zhanluxianshen. 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-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[aramase]

/triage accepted

/assign liggitt
(assigned as part of SIG Auth triage meeting)

This is not really a typo. Need to check if this is backward compatible or introduces any breaking changes.

[aramase]

/ok-to-test

[liggitt]

we got lucky, this is a repeated field, which is automatically optional in proto... this produced no change in the rbac generated.proto files or the generated pb.go files, so there is no impact to the proto wire compatibility

/lgtm
/approve
/milestone v1.31

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: e8957d45577da6dccc166af23d4eb6eb4c50ee80

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• staging/src/k8s.io/api/OWNERS [liggitt]

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

[zhanluxianshen]

😀,Thanks for review.

[zhanluxianshen]

/test pull-kubernetes-integration

[pacoxu]

/test pull-kubernetes-node-e2e-containerd