Thin-Pool Snapshooting Clarification #737
-
I noticed that with Thin-Pool Snapshotting enabled, there is a limitation on bound PVCs that I would like to explore: https://github.com/topolvm/topolvm/blob/main/docs/limitations.md#snapshots-should-be-created-only-for-a-bound-pvc I would like to understand the context of this. In which case would Thin-Pool Snapshotting not work? I am trying to reproduce a case where the "CSI Sanity" is skipped and I have a failing snapshot but I never managed to reproduce it. Does "WaitForFirstConsumer" on the storageclass skip this issue or is it irrelevant for scheduling in this case? I am using Kubernetes Capacity Scheduling, not the scheduler extension of TopoLVM Could you guide me on a setup on how to reproduce a Snapshot that would fail? Thanks in advance for any example, tip or guidance! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
A volume created by TopoLVM is bound to a specific node, and a snapshot of the volume is also bound to the same node. When you set the volume binding mode of TopoLVM's storage class to |
Beta Was this translation helpful? Give feedback.
@jakobmoellerdev
I tried it. As a result, I found that the snapshot became false status as I expected.
I temporarily edited the example Makefile as follows and run
make prepare-snap
.