-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
headlampUrl issue when deployed with backstage and ngnix ingress #8
Comments
Hey, You can configure the headlamp.url value to point to your url with subpath. |
we don't have headlamp deployed in cluster as separate instance. we are using backend Integration Mode. |
Since you are exposing headlamp via an Ingress you can use it in |
we don't have dedicated / separate headlamp deployment. headlamp backend is running in integrated mode (with backstage plugin itself). Doing so , FE tries to call https://devplatform.domain.com:4466 . which is causing problem. |
May I know what is happening in this case? Do you not see the Headlamp UI in the frontend or is it not loading the clusters from backstage to Headlamp? |
i'm trying to use this plugin in backstage instances that is deployed in k8s exposed via public ingress (nginx). having headlampUrl containing port 4466 & FE calling this headlampUrl from browser end , this port needs to be exposed via nginx.
exposing 4466 port is not recommended and straightforward from nginx ingress. can this headlampUrl be changed to something like:
file link
having default ports (80/443) with some path/uri , will enable reaching it via same backstage url and on some path.
The text was updated successfully, but these errors were encountered: