Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2753

DevWorkspace didn't take into account storage property of CheCluster when start workspace

XMLWordPrintable

    • False
    • False
    • Release Notes
    • Hide
      = Support for per-workspace storage strategy currently not available

      Currently, the `per-workspace` workspace storage strategy is not supported due to the change to the {devworkspace} engine. With migration from {prod-prev-short} 2.15 to {prod-short} {prod-ver}, existing workspaces change to the `common` strategy. Setting the PVC storage size other than 10 GB is currently not possible. There is currently no workaround for this issue.
      Show
      = Support for per-workspace storage strategy currently not available Currently, the `per-workspace` workspace storage strategy is not supported due to the change to the {devworkspace} engine. With migration from {prod-prev-short} 2.15 to {prod-short} {prod-ver}, existing workspaces change to the `common` strategy. Setting the PVC storage size other than 10 GB is currently not possible. There is currently no workaround for this issue.
    • Known Issue
    • Done

      There was DevWorkspace 2.16.0 instance created using CheCluster with next storage properties:

        storage:
    preCreateSubPaths: true
    pvcClaimSize: 2Gi
    pvcStrategy: per-workspace

      DevWorkspace was creating workspace with PersistentVolumeClaim of storage: 10Gi

      kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: claim-devworkspace
  namespace: admin-codeready
  uid: 9d9124b6-5b69-4442-84a8-3d51ba928048
  resourceVersion: '19115677'
  creationTimestamp: '2022-02-14T03:10:27Z'
  annotations:
    pv.kubernetes.io/bind-completed: 'yes'
    pv.kubernetes.io/bound-by-controller: 'yes'
    volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/cinder
    volume.kubernetes.io/selected-node: ocp49-dnochevn-66dfs-master-0
  finalizers:
    - kubernetes.io/pvc-protection
  managedFields:
    - manager: devworkspace-controller
      operation: Update
      apiVersion: v1
      time: '2022-02-14T03:10:27Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:spec':
          'f:accessModes': {}
          'f:resources':
            'f:requests':
              .: {}
              'f:storage': {}
          'f:volumeMode': {}
    - manager: kube-controller-manager
      operation: Update
      apiVersion: v1
      time: '2022-02-14T03:44:38Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:annotations':
            'f:pv.kubernetes.io/bind-completed': {}
            'f:pv.kubernetes.io/bound-by-controller': {}
            'f:volume.beta.kubernetes.io/storage-provisioner': {}
        'f:spec':
          'f:volumeName': {}
    - manager: kube-controller-manager
      operation: Update
      apiVersion: v1
      time: '2022-02-14T03:44:38Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:status':
          'f:accessModes': {}
          'f:capacity':
            .: {}
            'f:storage': {}
          'f:phase': {}
      subresource: status
    - manager: kube-scheduler
      operation: Update
      apiVersion: v1
      time: '2022-02-14T03:44:38Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:annotations':
            .: {}
            'f:volume.kubernetes.io/selected-node': {}
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi
  volumeName: pvc-9d9124b6-5b69-4442-84a8-3d51ba928048
  storageClassName: standard
  volumeMode: Filesystem
status:
  phase: Bound
  accessModes:
    - ReadWriteOnce
  capacity:
    storage: 10Gi

      Expected storage size: 2Gi

      An update: the issue has been reproduced with 'pvcStrategy: common', 'pvcClaimSize: 2Gi' in CheCluster in time of installation.

      Upstream issue: https://github.com/eclipse/che/issues/21405

              amisevsk Angel Misevski (Inactive)
              dnochevn Dmytro Nochevnov
              Max Leonov Max Leonov
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: