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

Gateway improvements suggestions #21182

Closed
1 task
l0rd opened this issue Feb 19, 2022 · 7 comments
Closed
1 task

Gateway improvements suggestions #21182

l0rd opened this issue Feb 19, 2022 · 7 comments
Labels
area/security kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months)

Comments

@l0rd
Copy link
Contributor

l0rd commented Feb 19, 2022 •
edited
Loading

Is your enhancement related to a problem? Please describe

  1. After idling there is no way to restart the workspace from the IDE: refreshing returns 503
  2. Every workspace pod includes a gateway (traefik). It blocks access from other namespaces to the workspace endpoints. But it also consume resources and increase startup time.
  3. Che default main URL has che repeated twice (che-eclipse-che.<k8s-gateway-hostname>)
  4. Workspaces main URLs are long: port and endpoint could be removed
  5. Workspaces URLs are not predictable: they could be identified by username, workspace name and port

Describe the solution you'd like
@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Feb 19, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Feb 19, 2022
@l0rd l0rd added roadmap/6-months Epics that are planned to complete in the medium term (within 6 months) kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. area/security and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Feb 19, 2022
@che-bot
Copy link
Contributor

che-bot commented Aug 19, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 19, 2022
@l0rd
Copy link
Contributor Author

l0rd commented Aug 19, 2022

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 19, 2022
@che-bot
Copy link
Contributor

che-bot commented Feb 15, 2023

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 15, 2023
@l0rd
Copy link
Contributor Author

l0rd commented Feb 15, 2023

/remove-lifecycle stale

@l0rd l0rd removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 15, 2023
@che-bot
Copy link
Contributor

che-bot commented Aug 14, 2023

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 14, 2023
@l0rd
Copy link
Contributor Author

l0rd commented Aug 14, 2023

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 14, 2023
@che-bot
Copy link
Contributor

che-bot commented Feb 10, 2024

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 10, 2024
@che-bot che-bot closed this as completed Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/security kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@l0rd @che-bot