# Ceph PersistentVolumeClaim Resizing

**URL:** <https://community.replicated.com/t/ceph-persistentvolumeclaim-resizing/409>\
**Category:** Packaging an application\
**Created:** [March 24, 2020, 3:27pm UTC](https://community.replicated.com/t/ceph-persistentvolumeclaim-resizing/409 "2020-03-24T15:27:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dex](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dex/32/26_2.png) [@dex](https://community.replicated.com/u/dex)\
**Post date:** [March 24, 2020, 3:27pm UTC](https://community.replicated.com/t/ceph-persistentvolumeclaim-resizing/409/1 "2020-03-24T15:27:25Z")

</div>

Often, it can be attractive to allow end users to configure the sizing of PVCs in a Kubernetes Cluster. While Rook/Ceph intends to support resizable PVCs in a future release, many kubernetes workload types that use PVCs, e.g. StatefulSet `volumeClaimTemplates` have immutable fields and do not support patching the volume claim size.

The recommendation in this case, when using Rook/Ceph-backed PVCs, is to request a volume much larger than the desired size. Because Rook PVCs are backed by an object store, they are sparse, and won’t actually consume disk space until that space is consumed in by the workload using the PVC.