Skip to content

Commit 4823c6c

Browse files
committed
Add storage access mode docs
Signed-off-by: dkwon17-test <[email protected]>
1 parent 6e8009c commit 4823c6c

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

docs/dwo-configuration.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,3 +106,22 @@ Cleanup CronJob configuration fields:
106106
- **`schedule`**: A Cron expression defining how often the cleanup job runs. Default: `"0 0 1 * *"` (first day of the month at midnight).
107107
- **`retainTime`**: The duration time in seconds since a DevWorkspace was last started before it is considered stale and eligible for cleanup. Default: 2592000 seconds (30 days).
108108
- **`dryRun`**: Set to `true` to run the cleanup job in dry-run mode. In this mode, the job logs which DevWorkspaces would be removed but does not actually delete them. Set to `false` to perform the actual deletion. Default: `false`.
109+
110+
## Configuring PVC storage access mode
111+
112+
By default, PVCs managed by the DevWorkspace Operator are created with the `ReadWriteOnce` access mode.
113+
The access mode can be configured with the `config.workspace.storageAccessMode` section of the global DWOC:
114+
115+
```yaml
116+
apiVersion: controller.devfile.io/v1alpha1
117+
kind: DevWorkspaceOperatorConfig
118+
metadata:
119+
name: devworkspace-operator-config
120+
namespace: $OPERATOR_INSTALL_NAMESPACE
121+
config:
122+
workspace:
123+
storageAccessMode:
124+
- ReadWriteMany
125+
```
126+
127+
The config above will have newly created PVCs to have its access mode set to `ReadWriteMany`.

0 commit comments

Comments
 (0)