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

Provide a config option to specify the statics path when running the Dashboard on a subpath using an Ingress rule (and controller) #3686

Closed
michaelajr opened this issue Mar 22, 2019 · 6 comments · Fixed by #8735
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@michaelajr
Copy link

Right now if you expose the Dashboard via an Ingress Controller and Ingress rule, and want to run the Dashboard on a subpath like /dashboard, statics can't load. This is because the URL for statics are embedded in the HTML as coming from the root. Most UI applications provide a way to start their app with a flag that specifies the application root so URLs are constructed properly in the page. This would be really nice to have for the Dashboard.

@floreks floreks added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/feature Categorizes issue or PR as related to a new feature. labels Mar 22, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 20, 2019
@michaelajr
Copy link
Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 20, 2019
@maciaszczykm
Copy link
Member

/lifecycle frozen

@michaelajr Would you be willing to work on that?

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jun 27, 2019
@webcoderz
Copy link

Would this solve: #5017? If so then it's a great idea!

@luchillo17
Copy link

I took a different approach with rewrite/redirect on the Ingress resource, hard to find, not documented anywhere & took me a whole week to figure out (barely know much of Ingress) #7616 (comment)

@floreks
Copy link
Member

floreks commented Mar 5, 2024

See my comment: #8053 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants