Replies: 1 comment
-
I'm not confident though, kube-scheduler is unrelated to snapshots, Yes.
The capacity annotation does not reflect actual space for thinpool and is not expected to be used by end users. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have fear of using overprovisioning. We plan to use snapshots, and this needs thin-pools. I read the docs, but still I am unsure.
In the thin-volumes proposal I read:
Up to now we plan to use the default capacity scheduler of Kubernetes, no the topolvm scheduler.
Imagine I have a 100 GB disk, and one VG and one thin-pool which use these 100 GB.
One PV uses 90 GB, and overprovisionedRatio is 1.0
Can a snapshot be created in this case?
If "Yes", then (thin-pool-size * overprovisionedRatio)-(sum-of-all-thin-lv-virtual-sizes-in-thin-pool) would be negative.
Is there a way to see the actual free disk space in an annotation, or is that only visible in the prometheus metrics?
Beta Was this translation helpful? Give feedback.
All reactions