Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Routes definition with tls-acme parsing problem - DNS-1123 subdomain must consist of lower case alphanumeric characters...
See original GitHub issueWe had a problem with the deployment when we had defined the tls-acme value in .lagoon.yml:
Error from server (Invalid): Route "vse.ch:\n tls-acme: 'false'" is invalid: [metadata.name: Invalid value: "vse.ch:\n tls-acme: 'false'": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'), spec.host: Invalid value: "vse.ch:\n tls-acme: 'false'": host must conform to DNS 952 subdomain conventions]
We have added the config as described here: https://lagoon.readthedocs.io/en/latest/using_lagoon/lagoon_yml/
Looks like that there is a problem with the line break.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
found it! thanks @twerthmueller and @marji for the help https://github.com/amazeeio/lagoon/pull/1007
@Schnitzel I send you the yaml over Slack.