K
Q

Persistent Volume Claim Kubernetes

1/28/2022

Kubectl version gives the following output.

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.5", GitCommit:"aea7bbadd2fc0cd689de94a54e5b7b758869d691", GitTreeState:"clean", BuildDate:"2021-09-15T21:04:16Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}

I have used kubectl to edit persistent volume from 8Gi to 30Gi as enter image description here

However, when I exec the pod and run df -h I see the following:

enter image description here

I have deleted the pods but it again shows the same thing. if I cd into cd/dev I don't see disk and vda1 folder there as well. I think I actually want the bitnami/influxdb to be 30Gi. Please guide and let me know if more info is needed.

-- Sami Hassan
diskspace
kubernetes
linux
persistent-volumes

Similar Questions

cni0 interface is missing in Kubernetes
How to merge ingress-nginx with existing nginx on worker node?
Kubelet Configuration
helm template: how do i assign the result of a template to a variable
How to set up GCP infrastructure to perform search quickly over massive set of json data?

1 Answer

2/11/2022

This is a community wiki answer posted for better visibility. Feel free to expand it.

Based on the comments provided here, there could be several reasons for this behavior.

  1. According to the documentation from the Kubernetes website, manually changing the PersistentVolume size will not change the volume size:

Warning: Directly editing the size of a PersistentVolume can prevent an automatic resize of that volume. If you edit the capacity of a PersistentVolume, and then edit the .spec of a matching PersistentVolumeClaim to make the size of the PersistentVolumeClaim match the PersistentVolume, then no storage resize happens. The Kubernetes control plane will see that the desired state of both resources matches, conclude that the backing volume size has been manually increased and that no resize is necessary.

  1. It also depends on how Kubernetes running and support for the allowVolumeExpansion feature. From DigitalOcean:

are you running one of DigitalOcean's managed clusters, or a DIY cluster running on DigitalOcean infrastructure? In case of the latter, which version of our CSI driver do you use? (You need v1.2.0 or later for volume expansion to be supported.)

-- Andrew Skorkin
Source: StackOverflow