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

Drop single user support on Che Server #20314

Closed
Tracked by #20326
, #20444
...
skabashnyuk opened this issue Aug 17, 2021 · 2 comments
Closed
Tracked by #20326
, #20444
...

Drop single user support on Che Server #20314

skabashnyuk opened this issue Aug 17, 2021 · 2 comments
Assignees
@xbaran4
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
Milestone
7.37

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Aug 17, 2021 •
edited by l0rd
Loading

Is your task related to a problem? Please describe

Drop single user support on Che Server

Describe the solution you'd like

Describe alternatives you've considered

No response

Additional context

Release Notes Text

The single user (unsecured) configuration of Che is not supported anymore. Che is a multi-tenant development workspace manager and there was no value to support a single user configuration. From now on, for single user scenarios users should consider deploying the DevWorkspace Operator without Che.
@skabashnyuk skabashnyuk added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Aug 17, 2021
@skabashnyuk skabashnyuk mentioned this issue Aug 17, 2021
Closed
@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 17, 2021
@skabashnyuk skabashnyuk added sprint/current and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. sprint/next labels Aug 17, 2021
@skabashnyuk skabashnyuk added this to the 7.36 milestone Aug 18, 2021
@skabashnyuk skabashnyuk mentioned this issue Aug 18, 2021
Closed
10 tasks
@xbaran4 xbaran4 mentioned this issue Aug 20, 2021
Merged
9 tasks
@skabashnyuk skabashnyuk mentioned this issue Aug 26, 2021
Merged
6 tasks
@l0rd l0rd added the new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes label Sep 7, 2021
@l0rd
Copy link
Contributor

l0rd commented Sep 7, 2021 •
edited
Loading

@skabashnyuk can we close this issue? And when we close it we should label it "status/release-notes-review-needed"

@sparkoo
Copy link
Member

sparkoo commented Sep 7, 2021

There's still PR open eclipse-che/che-server#89

@skabashnyuk skabashnyuk modified the milestones: 7.36, 7.37 Sep 8, 2021
@skabashnyuk skabashnyuk mentioned this issue Sep 8, 2021
Closed
14 tasks
@skabashnyuk skabashnyuk added the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Sep 9, 2021
@max-cx max-cx removed the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xbaran4 xbaran4

Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
Projects
None yet
Milestone
7.37
Development

No branches or pull requests
6 participants
@l0rd @sparkoo @skabashnyuk @che-bot @xbaran4 @max-cx