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

Failed to create Knative Service #605

Open
dprotaso opened this issue Sep 3, 2021 · 2 comments
Open

Failed to create Knative Service #605

dprotaso opened this issue Sep 3, 2021 · 2 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@dprotaso
Copy link
Contributor

dprotaso commented Sep 3, 2021

net-contour get's into a weird state when I try to create a service with a single character name

kn service create a --image gcr.io/knative-samples/helloworld-go --env TARGET=A

The logs show

HTTPProxy.projectcontour.io \"a--ep-contour-internal-6baf84cb4382b42fab34fb571f9b82a9a-00001.\" is invalid: metadata.name: Invalid value: \"a--ep-contour-internal-6baf84cb4382b42fab34fb571f9b82a9a-00001.\": a lowercase RFC 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])?)*')

It seems like it should actually be valid based on the regex - https://regex101.com/r/KiCvWq/1

Either way since we can't create the HTTPProxy we should probably set Ready=False on the Ingress to bubble this up that the Service failed

@github-actions
Copy link

github-actions bot commented Dec 3, 2021

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 3, 2021
@dprotaso
Copy link
Contributor Author

dprotaso commented Dec 3, 2021

/lifecycle frozen

@knative-prow-robot knative-prow-robot 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 Dec 3, 2021
@dprotaso dprotaso added this to the test milestone Feb 10, 2022
@nak3 nak3 modified the milestones: test, v1.4.0 Mar 9, 2022
@carlisia carlisia removed this from the v1.4.0 milestone Jun 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

4 participants