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

Add ability to configure ephemeral mode for workspaces from dashboard #12374

Closed
ashumilova opened this issue Jan 10, 2019 · 5 comments
Closed
Assignees
Labels
status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@ashumilova
Copy link
Contributor

There is attribute, that allows to configure workspace to be ephemeral with no PVC attached on K8S/OpenShift infrastructure, so the aim of the issue is to allow configure that attribute from UI of User Dashboard.
Attribute name is persistVolumes, that shoud be set in workspace configuration.

@ashumilova ashumilova added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. sprint/next team/ide2 labels Jan 10, 2019
@ashumilova ashumilova self-assigned this Jan 10, 2019
@slemeur
Copy link
Contributor

slemeur commented Jan 14, 2019

Can be on the workspace overview page.

@sleshchenko
Copy link
Member

@ashumilova Should we close it since the corresponding PR is merged?

@ibuziuk
Copy link
Member

ibuziuk commented Feb 14, 2019

@ashumilova @slemeur @l0rd is it planned to add ephemeral trigger to the create-workspace view ? currently IMO it is hidden and as I understand we want to encourage / make default ephemeral workspace creation (at least on che.openshift.io)

@slemeur
Copy link
Contributor

slemeur commented Feb 14, 2019

@ibuziuk : I don't think it should be done in upstream.
We should have a dedicated task to handle that for the case of che.openshift.io.

@ibuziuk
Copy link
Member

ibuziuk commented Feb 14, 2019

hmm... but why not to add the toggle (disabled by default) in the upstream, and just enable it by default in downstream ? IMO it is really logical and I guess it was smth. we have discussed with @l0rd (or maybe I got wrong idea)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Development

No branches or pull requests

4 participants