Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Done
Priority: Major
Fix Version/s: DWO 0.35.1, 3.23.0.GA
Affects Version/s: None
Component/s: Team B: Dev Spaces operator + chectl/dsc, DevWorkspace + Operator, Web Terminal + Operator, Universal Developer Image, machine-exec, dev environment config
Labels:

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Affects:

Release Notes
Release Note Text:

Hide
= `ReadWriteMany` access mode now configurable for persistent volume claims

You can now configure the storage access mode for persistent volume claims (PVCs) from the `CheCluster` custom resource. This is useful when mounting one per-user PVC to multiple running CDE pods. To enable the `ReadWriteMany` access mode, apply the following configuration in the `CheCluster` custom resource:

[source,yaml]
----
apiVersion: org.eclipse.che/v2
kind: CheCluster
metadata:
  name: devspaces
  namespace: openshift-devspaces
spec:
  devEnvironments:
      storage:
      pvcStrategy: per-user
      perUserStrategyPvcConfig:
        storageAccessMode:
        - ReadWriteMany
----
<1> Set the value to `ReadWriteMany` for RWX support

After you apply this configuration, new per-user PVCs will use the `ReadWriteMany` access mode.

[NOTE]
====
The `ReadWriteMany` access mode only works if the underlying storage class supports RWX volume capabilities. For example, Amazon EBS supports only `ReadWriteOnce`. In this case, creating a PVC with `ReadWriteMany` will not work.
====

Show
= `ReadWriteMany` access mode now configurable for persistent volume claims You can now configure the storage access mode for persistent volume claims (PVCs) from the `CheCluster` custom resource. This is useful when mounting one per-user PVC to multiple running CDE pods. To enable the `ReadWriteMany` access mode, apply the following configuration in the `CheCluster` custom resource: [source,yaml] ---- apiVersion: org.eclipse.che/v2 kind: CheCluster metadata:   name: devspaces   namespace: openshift-devspaces spec:   devEnvironments:       storage:       pvcStrategy: per-user       perUserStrategyPvcConfig:         storageAccessMode:         - ReadWriteMany ---- <1> Set the value to `ReadWriteMany` for RWX support After you apply this configuration, new per-user PVCs will use the `ReadWriteMany` access mode. [NOTE] ==== The `ReadWriteMany` access mode only works if the underlying storage class supports RWX volume capabilities. For example, Amazon EBS supports only `ReadWriteOnce`. In this case, creating a PVC with `ReadWriteMany` will not work. ====
Release Note Type:
Enhancement
Release Note Status:
Done
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

I believe documentation is clear about pvcStrategy and I can understand the performance consequences this RFE could have. Also the customer has been warned about this. Anyway, I am reporting this request to have it evaluated by engineering.

It would be interesting for certain customers to be able to specify if the persistent volume should be RWO or RWX when using pvcStrategy per-user.
=====================================

the idea is that when a user is creating more than one workspace, and using as pvc strategy per-user, we could re-use the volume and when the workspace is scheduled in different nodes, we don't have this issue:

53s Warning FailedAttachVolume pod/workspacexxxxxx-yyyy Multi-Attach error for volume "pvc-zzzzzz" Volume is already used by pod(s) workspaceaaaaaaaaaaaaaaaaaaaaaaaaaa-bbbb,
workspacebbbbbbbbbbbbbbbbbbbbbbbb-cccc,
workspacedddddddddddddddddddd-eeee