mirror of
https://github.com/ceph/ceph-csi.git
synced 2024-11-10 00:10:20 +00:00
8ebc0659ab
For static volume, the user will manually mounts already existing image as a volume to the application pods. As its a rbd Image, if the PVC is of type fileSystem the image will be mapped, formatted and mounted on the node, If the user resizes the image on the ceph cluster. User cannot not automatically resize the filesystem created on the rbd image. Even if deletes and recreates the kubernetes objects, the new size will not be visible on the node. With this changes During the NodeStageVolumeRequest the nodeplugin will check the size of the mapped rbd image on the node using the devicePath. and also the rbd image size on the ceph cluster. If the size is not matching it will do the file system resize on the node as part of the NodeStageVolumeRequest RPC call. The user need to do below operation to see new size * Resize the rbd image in ceph cluster * Scale down all the application pods using the static PVC. * Make sure no application pods which are using the static PVC is running on a node. * Scale up all the application pods. Validate the new size in application pod mounted volume. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> |
||
|---|---|---|
| .. | ||
| design/proposals | ||
| capabilities.md | ||
| ceph-csi-upgrade.md | ||
| coding.md | ||
| DCO | ||
| deploy-cephfs.md | ||
| deploy-rbd.md | ||
| development-guide.md | ||
| disaster-recovery.md | ||
| expand-pvc.md | ||
| metrics.md | ||
| rbd-nbd.md | ||
| releases.md | ||
| resource-cleanup.md | ||
| snap-clone.md | ||
| static-pvc.md | ||