Fix typo in the --anonymous-auth flag name

[LucaBernstein]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Fix a typo in an error message during apiserver authentication.

Which issue(s) this PR 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: LucaBernstein / (74167f9)

The committers listed above are authorized under a signed CLA.

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

[k8s-ci-robot]

Welcome @LucaBernstein!

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

[seans3]

/ok-to-test

@LucaBernstein Thanks for your contribution. This error message change may be an API change. If it is, there are several requirements to merge it, including deprecating the error message across multiple releases. Please check with SIG API Machinery to determine if this requires the full flag API change mechanism. Thanks :)

[ialidzhikov]

@LucaBernstein Thanks for your contribution. This error message change may be an API change. If it is, there are several requirements to merge it, including deprecating the error message across multiple releases. Please check with SIG API Machinery to determine if this requires the full flag API change mechanism. Thanks :)

I am not quite sure this indeed classifies as API change. There is no value doing deprecations in this particular case. How would you do this at all?

[ialidzhikov]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: d70da8ddbfa1870cce25323c7ff1d076326a39ec

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ialidzhikov, LucaBernstein
Once this PR has been reviewed and has the lgtm label, please assign jpbetz for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• pkg/kubeapiserver/OWNERS

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

[ialidzhikov]

/test pull-kubernetes-unit

[ialidzhikov]

/cc @dims

[ialidzhikov]

/cc @liggitt