Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/dwo-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -106,3 +106,22 @@ Cleanup CronJob configuration fields:
- **`schedule`**: A Cron expression defining how often the cleanup job runs. Default: `"0 0 1 * *"` (first day of the month at midnight).
- **`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).
- **`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`.

## Configuring PVC storage access mode

By default, PVCs managed by the DevWorkspace Operator are created with the `ReadWriteOnce` access mode.
The access mode can be configured with the `config.workspace.storageAccessMode` section of the global DWOC:

```yaml
apiVersion: controller.devfile.io/v1alpha1
kind: DevWorkspaceOperatorConfig
metadata:
name: devworkspace-operator-config
namespace: $OPERATOR_INSTALL_NAMESPACE
config:
workspace:
storageAccessMode:
- ReadWriteMany
```

The config above will have newly created PVCs to have its access mode set to `ReadWriteMany`.
Copy link
Copy Markdown
Member

@rohanKanojia rohanKanojia Jun 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also mention the default value of this field if nothing is specified, ReadWriteOnce .

Sorry, I missed that it's already specified in the first sentence.

Loading