-
Notifications
You must be signed in to change notification settings - Fork 62
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
Backstage component is not deployed as service and no ingress route is available #22
Labels
bug
Something isn't working
Comments
I included the following service and ingress yaml to the existing backstage yaml
but cannot access the URL:
|
I fixed this issue here: cnoe-io/backstage-app#13 |
Merged
jessesanford
added a commit
that referenced
this issue
Oct 19, 2023
* Adding the definition about the Service and Ingress kubernetes resource to expose backstage using the host: backstage.idpbuilder.cnoe.io.local Signed-off-by: cmoulliard <[email protected]> * Changing localhost host name to https://backstage.idpbuilder.cnoe.io.local:8443 to avoid the error: backstage/backstage#15403 Signed-off-by: cmoulliard <[email protected]> * Switching the DNS name from cnoe.io.local to cnoe.io.localtest.me Signed-off-by: cmoulliard <[email protected]> --------- Signed-off-by: cmoulliard <[email protected]> Co-authored-by: cmoulliard <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue
The backstage component is not deployed as a service and no ingress route is published too
The text was updated successfully, but these errors were encountered: