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

Reduce number of ConfigMaps for gateway single-host #17669

Closed
sparkoo opened this issue Aug 20, 2020 · 2 comments
Closed

Reduce number of ConfigMaps for gateway single-host #17669

sparkoo opened this issue Aug 20, 2020 · 2 comments
Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@sparkoo
Copy link
Member

sparkoo commented Aug 20, 2020 •
edited
Loading

Is your enhancement related to a problem? Please describe.

#17060 will introduce gateway based exposure for single-host strategy. For that, we create a Configmap in che installation namespace for every exposed server, that means at least 7 configmaps per running workspace (possibly more, depends on the devfile). This may become a bottleneck to have so many configmaps in one namespace.

Describe the solution you'd like

Merge all gateway configurations of single workspace into single configmap.

Describe alternatives you've considered

Additional context

#17060
epic: #12914
@sparkoo sparkoo added kind/enhancement A feature request - must adhere to the feature request template. area/che-server labels Aug 20, 2020
@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 Aug 20, 2020
@l0rd l0rd mentioned this issue Aug 20, 2020
Closed
35 tasks
@sparkoo sparkoo mentioned this issue Aug 20, 2020
Merged
@nickboldt
Copy link
Contributor

which team will work on this? can you assign it to that team's / area's label?

@amisevsk amisevsk added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 21, 2020
@che-bot
Copy link
Contributor

che-bot commented Feb 24, 2021

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 24, 2021
@che-bot che-bot closed this as completed Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@nickboldt @sparkoo @amisevsk @che-bot