Skip to content
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

Closed
mcfedr opened this issue Jan 17, 2019 · 5 comments
Closed

Sync error when ingress name has dots #614

mcfedr opened this issue Jan 17, 2019 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@mcfedr
Copy link
Contributor

mcfedr commented Jan 17, 2019

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 like

Error during sync: Error running load balancer syncing routine: googleapi: Error 400: Invalid value 'k8s-um-default-some.home.com-ingress--521bdf95908d2d0'. Values must match the following regular expression: '[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?', invalidParameter

This mismatch of valid values could be handled by the controller

@bowei
Copy link
Member

bowei commented Jan 17, 2019

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

@rramkumar1
Copy link
Contributor

For tracking purposes, marking this as a bug but as bowei said, we may not fix this.

/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jan 22, 2019
@mcfedr
Copy link
Contributor Author

mcfedr commented Jan 22, 2019

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.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2019
@rramkumar1 rramkumar1 added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 29, 2019
@swetharepakula
Copy link
Member

Closing, as we will not be adding support for this.

@swetharepakula swetharepakula closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

6 participants