che icon indicating copy to clipboard operation
che copied to clipboard

Fail to start a workspace if storage hasn't been configured on the cluster

Open l0rd opened this issue 5 years ago • 11 comments

Is your enhancement related to a problem? Please describe.

We should check if dynamic storage and extra persistent volumes have been configured on a cluster before letting the user create a workspace. And propose to start the workspace in ephemeral mode.

l0rd avatar Jun 25 '20 13:06 l0rd

@l0rd can you give a few examples of expected from the che-server activity. I do not fully understand this request.

skabashnyuk avatar Jul 07 '20 09:07 skabashnyuk

e.g. PVC quota in the user namespace

ibuziuk avatar Jul 07 '20 10:07 ibuziuk

OC 3.11

oc  describe quota object-counts  -n skabashn-che
Name:                   object-counts
Namespace:              skabashn-che
Resource                Used  Hard
--------                ----  ----
persistentvolumeclaims  1     2
replicationcontrollers  0     20
secrets                 18    20
services                0     15

skabashnyuk avatar Jul 07 '20 10:07 skabashnyuk

so, this ^ means if a user is not allowed to create PVC workspace startup should be prohibited in the non-ephemeral mode.

ibuziuk avatar Jul 07 '20 10:07 ibuziuk

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 avatar Jan 20 '21 11:01 che-bot

This should be fixed with devworkspace as workspace engine. I beleive that's a check that dashbord should do. Changing the area label accordingly and setting devworkspace STEP 3 as milestone. cc @sleshchenko

l0rd avatar Jun 18 '21 14:06 l0rd

After discussion at latest dw cabal we decided to remove this issue from the scope of milestone "DevWorkspace Integration - STEP3".

l0rd avatar Sep 08 '21 09:09 l0rd

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 avatar Mar 07 '22 00:03 che-bot

/remove-lifecycle stale

l0rd avatar Mar 14 '22 11:03 l0rd

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 avatar Sep 10 '22 00:09 che-bot

lifecycle/frozen

ibuziuk avatar Jun 11 '24 10:06 ibuziuk