-
Notifications
You must be signed in to change notification settings - Fork 297
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
Sync error when ingress name has dots #614
Comments
We may elect to not fix this as the munging the dots into underscores in the name can result aliasing issues for the GCP objects, unless there are a lot of users in this situation... |
For tracking purposes, marking this as a bug but as bowei said, we may not fix this. /kind bug |
Fair enough, i thought that might be the case, but still useful to know about it and for others to be able to find it. |
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. |
Closing, as we will not be adding support for this. |
Its valid for kubernetes resources to have dots in the names, so an ingress with a name like
some.host.com-ingress
is valid, but the gce ingress fails when you create such an ingress, with an error likeThis mismatch of valid values could be handled by the controller
The text was updated successfully, but these errors were encountered: