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.

Sign up for GitHub

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

Jump to bottom

Configurable path prefix #8224

Closed
jkroepke opened this issue Aug 25, 2023 · 8 comments · Fixed by #8735
Closed

Configurable path prefix #8224

jkroepke opened this issue Aug 25, 2023 · 8 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.

Comments

@jkroepke
Copy link
Contributor

What would you like to be added?

Please add the possible to run the Kubernetes api and web under different web prefixes, like

Why is this needed?

I would like to run all my management tools under the same domain.

If possible, any cookies created by the dashboard should also have the prefix inside it.
@jkroepke jkroepke added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 25, 2023
@floreks
Copy link
Member

floreks commented Sep 1, 2023 •
edited
Loading

We could potentially allow frontend to be served under a different subpath, but the API path is required to be accessible as a subpath of the UI right now. This means that if web will be accessible under xyz.com/dashboardui then API has to be available under xyz.com/dashboardui/api. This is currently a hard requirement.

@jkroepke
Copy link
Contributor Author

jkroepke commented Sep 1, 2023

That fine for me.

@jkroepke
Copy link
Contributor Author

jkroepke commented Sep 4, 2023

I make the setup having the dashboard behind a reverse proxy more simple. Currently. I have to deal with rewrite rules on nginx

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Jan 27, 2024
@jkroepke
Copy link
Contributor Author

Up

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 26, 2024
@jkroepke
Copy link
Contributor Author

Up

@maciaszczykm maciaszczykm added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Feb 26, 2024
@floreks
Copy link
Member

floreks commented Mar 5, 2024

See my comment: #8053 (comment)

@floreks floreks mentioned this issue Mar 5, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: update helm chart to work with kong as a gateway kubernetes/dashboard
5 participants
@jkroepke @floreks @maciaszczykm @k8s-ci-robot @k8s-triage-robot