-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: username or group is not a DNS-1123 hostname #80
Comments
@nckturner @mattmoyer I was digging into the username fields in https://github.com/kubernetes/kubernetes and it doesn't look like they have any validation on the field. Do you know of anything different? |
I just ran into this issue. I do not see anything in Kubernetes that says that usernames have the restrictions that this project imposes. The closest thing I could find is the restrictions on resource names, and labels. Furthermore, our current setup uses users with "Firstname Lastname" as their username, which doesn't match DNS-1123. In the official documentation, the sample username is an email address (which we would like to move to), which also does not match DNS-1123. I think this bit of validation needs to be removed. From what I can tell, I think we just need to edit this code as follows:
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
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. |
I ran into this as well. Given that k8s doesn't place a dns-1123 restriction on usernames or groups I definitely think this check as well as the replacement of Additionally the current regex used to check if a user/group name is conforming contains an error.
The expression isn't end/beginning of line anchored so it will match any string that contains a sub-string that is a valid dns-1123 name. /reopen |
@richardmarshall: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
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. |
I am seeing this error by largely following the documentation. Groups in example.yaml and from the Kubernetes docs typically have a colon in them. For example
system:masters
. However, this is failing authentication because they don't conform. I am not sure whether I should be changing the group name or if this constraint is either in the wrong place or should be removed altogether?The text was updated successfully, but these errors were encountered: