<p><code>Kubectl version</code> gives the following output.</p>
<pre><code>Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;22&quot;, GitVersion:&quot;v1.22.4&quot;, GitCommit:&quot;b695d79d4f967c403a96986f1750a35eb75e75f1&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2021-11-17T15:48:33Z&quot;, GoVersion:&quot;go1.16.10&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;21&quot;, GitVersion:&quot;v1.21.5&quot;, GitCommit:&quot;aea7bbadd2fc0cd689de94a54e5b7b758869d691&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2021-09-15T21:04:16Z&quot;, GoVersion:&quot;go1.16.8&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
</code></pre>
<p>I have used <code>kubectl</code> to edit persistent volume from 8Gi to 30Gi as <a href="https://i.stack.imgur.com/xYH2o.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/xYH2o.png" alt="enter image description here" /></a></p>
<p>However, when I exec the pod and run <code>df -h</code> I see the following:</p>
<p><a href="https://i.stack.imgur.com/n02oH.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/n02oH.png" alt="enter image description here" /></a></p>
<p>I have deleted the pods but it again shows the same thing. if I <code>cd</code> into <code>cd/dev</code> I don't see disk and <code>vda1</code> folder there as well. I think I actually want the <code>bitnami/influxdb</code> to be 30Gi. Please guide and let me know if more info is needed.</p>

Sami Hassan
<p><em>This is a community wiki answer posted for better visibility. Feel free to expand it.</em></p>
<p>Based on the comments provided here, there could be several reasons for this behavior.</p>
<ol>
<li>According to the documentation from the <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims" rel="nofollow noreferrer">Kubernetes website</a>, manually changing the PersistentVolume size will not change the volume size:</li>
</ol>
<blockquote>
<p><strong>Warning:</strong> 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.</p>
</blockquote>
<ol>
<li>It also depends on how Kubernetes running and support for the <code>allowVolumeExpansion</code> feature. From <a href="https://github.com/digitalocean/csi-digitalocean/issues/291#issuecomment-598783816" rel="nofollow noreferrer">DigitalOcean</a>:</li>
</ol>
<blockquote>
<p>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.)</p>
</blockquote>
