Cannot configure anonymous auth in `--authentication-config` file

[brandond]

Environmental Info:
K3s Version: n/a

Node(s) CPU architecture, OS, and Version:
n/a

Cluster Configuration:
n/a

Describe the bug:
Follow up to

• Cannot start k3s with authorization-config apiserver flag set #12017

With the change from #12018 we can now set --authentication-config, however if the authentication config file contains an anonymous field the apiserver will exit with an error, as anonymous auth cannot be configured when the --anonymous-auth CLI flag is set.

Steps To Reproduce:
See RKE2 issue:

• Cannot use Anonymous Authenticator Configuration rancher/rke2#8137

Expected behavior:
Can configure anonymous auth via config file

Actual behavior:
Cannot configure anonymous auth via config file

Additional context / logs:
Should probably make the flag conditional on authentication-config not being set, same as authorization-mode.

[fmoral2]

getting same error on 133 and 132

 level=error msg="apiserver exited: anonymous: Forbidden: --anonynous-auth flag cannot be set when anonymous field is configured in authentication configuration file"



msg="Not setting kube-apiserver 'authorization-mode' and 'anonymous-auth' flags due to user-provided 'authorization-config' file."

talked with @brandond already who is going to add a fix

[brandond]

I stopped reading at the --anonynous-auth typo in the error message and didn't notice that this is regarding the authentication configuration file, not the authorization config file. Will fix.