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.

Sign up for GitHub

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

Jump to bottom

long route name in .lagoon.yml causes ingress to fail creating #2379

Closed
twardnw opened this issue Dec 4, 2020 · 1 comment · Fixed by #2582
Closed

long route name in .lagoon.yml causes ingress to fail creating #2379

twardnw opened this issue Dec 4, 2020 · 1 comment · Fixed by #2582
Labels
2-build-deploy Build & Deploy subsystem
Milestone
v1.13.2

Comments

@twardnw
Copy link
Contributor

twardnw commented Dec 4, 2020

The chart for custom ingresses attempts to use the hostname of a route as the name of the release. The release name is limited to 53 characters, so even though hostnames which are longer than this are perfectly valid, this causes a failure in the deploy of such routes.
@Schnitzel Schnitzel added the 2-build-deploy Build & Deploy subsystem label Jan 20, 2021
@Schnitzel Schnitzel added this to the v1.13.2 milestone Jan 20, 2021
@dasrecht dasrecht mentioned this issue Mar 3, 2021
Closed
Schnitzel added a commit that referenced this issue Mar 23, 2021
@Schnitzel
#2379: trim routes that are longer than 53 for usage in helm release …
1b42996 
…name
@Schnitzel Schnitzel mentioned this issue Mar 23, 2021
Merged
@rocketeerbkw
Copy link
Member

Fixed in 2.x with #2596

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2-build-deploy Build & Deploy subsystem
Projects
None yet
Milestone
v1.13.2
Development

Successfully merging a pull request may close this issue.

trim routes that are longer than 53 for usage in helm release name uselagoon/lagoon
3 participants
@rocketeerbkw @twardnw @Schnitzel