Re: [kubernetes/kubernetes] Can PVC show used/available size? (#42465)
Michail Kargakis
@kubernetes/sig-storage-feature-requests
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Jing Xu
I plan to work on this feature, assign to myself.
Killy
does the capacity work well ? when the volume size more than the capacity, there is nothing happened, why?
Jan Šafránek
@killy001, PVC.spec.capacity is user's request for storage, "I want 10 GiB volume". PV.spec.capacity is actual size of the PV. PVC can bind to a bigger PV when there is no smaller available PV, so the user can get actually more than he wants.
Similarly, dynamic provisioning works typically in bigger chunks. So if user asks for 0.5GiB in a PVC, he will get 1 GiB PV because that's the smallest one that AWS can provision.
There is nothing wrong about it.
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
Jing Xu
/remove-lifecycle stale
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
fejta-bot
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
k8s-ci-robot
Closed #42465.
Jose A. Iñigo
/reopen
k8s-ci-robot
@codependent: You can't reopen an issue/PR unless you authored it or you are a collaborator.
In response to this:
/reopen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Harrison Heck
This would be really useful.
Killy
@jsafrane I know what you said, but i am wondering when user actually used more than the binded pv capacity,what will happened?
Jan Šafránek
It's up to storage driver to decide. In case of a block volume, write() will probably fail. Kubernetes does not do any checking here.
Hamdan Radaideh
this feature is needed .. !!!!
@jingxu97
ntsh999
this is a much required feature!
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Appréderisse Benjamin
Is there a way to get that information programmatically using the metrics api?
Hamdan Al-Radaideh
well it depend on the provisioner
for example Ceph have a long workaround to get the size of the image (PV)
i made an integration with Ceph/k8s/Prometheus here https://github.com/halradaideh/size_exporter
I think a DaemonSet replicaset, can have access to the mounted paths on each node, and simple check the size using a Linux utility like DH, then map them to the PVs..