Skip to content

Commit 8bf8eb4

Browse files
mayastor-borsdsharma-dc
andcommitted
chore(bors): merge pull request #728
728: chore: tunable for allowing non-persistent devpath for disks r=dsharma-dc a=dsharma-dc Co-authored-by: Diwakar Sharma <[email protected]>
2 parents 07c5a6a + a64d454 commit 8bf8eb4

File tree

3 files changed

+7
-0
lines changed

3 files changed

+7
-0
lines changed

chart/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,7 @@ This removes all the Kubernetes components associated with the chart and deletes
6666

6767
| Key | Description | Default |
6868
|:----|:------------|:--------|
69+
| agents.&ZeroWidthSpace;core.&ZeroWidthSpace;allowNonPersistentDevlink | Allow using non-persistent kernel devpaths for pool disks. Enabling this will let users to use the kernel devpaths e.g /dev/sda, for diskpools. However, this comes with associated risks if the devpaths get swapped among disks, resulting in total data loss especially if encryption is being used. | `false` |
6970
| agents.&ZeroWidthSpace;core.&ZeroWidthSpace;capacity.&ZeroWidthSpace;thin.&ZeroWidthSpace;poolCommitment | The allowed pool commitment limit when dealing with thin provisioned volumes. Example: If the commitment is 250 and the pool is 10GiB we can overcommit the pool up to 25GiB (create 2 10GiB and 1 5GiB volume) but no further. | `"250%"` |
7071
| agents.&ZeroWidthSpace;core.&ZeroWidthSpace;capacity.&ZeroWidthSpace;thin.&ZeroWidthSpace;snapshotCommitment | When creating snapshots for an existing volume, each replica pool must have at least this much free space percentage of the volume size. Example: if this value is 40, the pool has 40GiB free, then the max volume size allowed to be snapped on the pool is 100GiB. | `"40%"` |
7172
| agents.&ZeroWidthSpace;core.&ZeroWidthSpace;capacity.&ZeroWidthSpace;thin.&ZeroWidthSpace;volumeCommitment | When creating replicas for an existing volume, each replica pool must have at least this much free space percentage of the volume size. Example: if this value is 40, the pool has 40GiB free, then the max volume size allowed to be created on the pool is 100GiB. | `"40%"` |

chart/templates/mayastor/agents/core/agent-core-deployment.yaml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,8 @@ spec:
7474
- "--no-volume-health"{{ end }}
7575
{{- if eq .Values.agents.core.encryptedPoolsSoftScheduling true }}
7676
- "--encrypted-pools-soft-scheduling"{{- end }}
77+
{{- if eq .Values.agents.core.allowNonPersistentDevlink true}}
78+
- "--allow-non-persistent-devlink"{{- end }}
7779
ports:
7880
- containerPort: 50051
7981
env:

chart/values.yaml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -209,6 +209,10 @@ agents:
209209
# If a volume wasn't provisioned with a encryption storageclass, we try to place the replicas of such volume on best-effort basis onto encrypted pools, if this global is set.
210210
# This is effective subject to volume spec already modified via plugin to request encryption.
211211
encryptedPoolsSoftScheduling: false
212+
# -- Allow using non-persistent kernel devpaths for pool disks.
213+
# Enabling this will let users to use the kernel devpaths e.g /dev/sda, for diskpools. However, this comes with associated risks if the devpaths
214+
# get swapped among disks, resulting in total data loss especially if encryption is being used.
215+
allowNonPersistentDevlink: false
212216
ha:
213217
enabled: true
214218
node:

0 commit comments

Comments
 (0)