Skip to content

Add warning admonition on working with local data. #143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Gerrit91 merged 2 commits into from
Jan 8, 2026
Merged

Add warning admonition on working with local data. #143

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bb7f225
Add warning admonition on working with local data.
Gerrit91 Jan 8, 2026
089ab04
Indent.
Gerrit91 Jan 8, 2026
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
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,9 @@ Underneath it creates a LVM logical volume on the local disks. A comma-separated

This CSI driver is derived from [csi-driver-host-path](https://github.com/kubernetes-csi/csi-driver-host-path) and [csi-lvm](https://github.com/metal-stack/csi-lvm)

> [!WARNING]
> Note that there is always an inevitable risk of data loss when working with local volumes. For this reason, be sure to back up your data or implement proper data replication methods when using this CSI driver.

## Currently it can create, delete, mount, unmount and resize block and filesystem volumes via lvm ##

For the special case of block volumes, the filesystem-expansion has to be performed by the app using the block device
Expand Down
6 changes: 3 additions & 3 deletions charts/csi-driver-lvm/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,9 +62,9 @@ nodeSelector:
# so it is not necessary to set a nodeSelector for it

# plugin:
# node-role.kubernetes.io/master: ""
# Key name may need to be updated to 'node-role.kubernetes.io/control-plane'
# in the future
# node-role.kubernetes.io/master: ""
# # Key name may need to be updated to 'node-role.kubernetes.io/control-plane'
# # in the future

# The provisioner has an affinity for nodes with a plugin pod,
# but since that's a daemonset, we allow more fine-grained node selection
Expand Down