<p>I just installed redis (actually a reinstall and upgrade) on GKE via helm.  It was a pretty standard install and nothing too out of the norm.   Unfortunately my &quot;redis-master&quot; container logs are showing sync errors over and over again:</p>
<pre><code>Info 2022-02-01 12:58:22.733 MST redis1:M 01 Feb 2022 19:58:22.733 * Waiting for end of BGSAVE for SYNC
Info 2022-02-01 12:58:22.733 MST redis 8085:C 01 Feb 2022 19:58:22.733 # Write error saving DB on disk: No space left on device
Info 2022-02-01 12:58:22.830 MST redis 1:M 01 Feb 2022 19:58:22.829 # Background saving error
Info 2022-02-01 12:58:22.830 MST redis 1:M 01 Feb 2022 19:58:22.829 # Connection with replica redis-replicas-0.:6379 lost.
Info 2022-02-01 12:58:22.830 MST redis 1:M 01 Feb 2022 19:58:22.829 # SYNC failed. BGSAVE child returned an error
Info 2022-02-01 12:58:22.830 MST redis 1:M 01 Feb 2022 19:58:22.829 # Connection with replica redis-replicas-1.:6379 lost.
Info 2022-02-01 12:58:22.830 MST redis 1:M 01 Feb 2022 19:58:22.829 # SYNC failed. BGSAVE child returned an error
Info 2022-02-01 12:58:22.832 MST redis 1:M 01 Feb 2022 19:58:22.832 * Replica redis-replicas-0.:6379 asks for synchronization
Info 2022-02-01 12:58:22.832 MST redis 1:M 01 Feb 2022 19:58:22.832 * Full resync requested by replica redis-replicas-0.:6379
Info 2022-02-01 12:58:22.832 MST redis 1:M 01 Feb 2022 19:58:22.832 * Starting BGSAVE for SYNC with target: disk
Info 2022-02-01 12:58:22.833 MST redis 1:M 01 Feb 2022 19:58:22.833 * Background saving started by pid 8086
</code></pre>
<p>I then looked at my persistent volume claim specification &quot;redis-data&quot; and it is in the &quot;Pending&quot; Phase and never seems to get out of that phase.  If I look at all my PVCs though then they are all bound and appear to be healthy.</p>
<p>Clearly something isn't as healthy as it seems but I am not sure how to diagnose.  Any help would be appreciated.</p>

mornindew
<p>i know it late to the party but to add more if any of get stuck into the same scenario and <strong>can't</strong> delete the <strong>PVC</strong> they can increase <strong>size of the PVC</strong> in <strong>GKE</strong>.</p>
<p>Check <strong>storageclass</strong> :</p>
<pre><code>apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
 …
provisioner: kubernetes.io/gce-pd
allowVolumeExpansion: true
</code></pre>
<p>Edit the <strong>PVC</strong></p>
<pre><code>spec:
   accessModes:
     - ReadWriteOnce
   resources:
     requests:
       storage: 10Gi
</code></pre>
<p><strong>Field</strong> that you need to update in <strong>PVC</strong></p>
<pre><code>spec:
   accessModes:
     - ReadWriteOnce
   resources:
     requests:           &lt;== make sure in requests section
       storage: 30Gi     &lt;=========
</code></pre>
<p>Once changes are applied for <strong>PVC</strong> and saved just <strong>Restart</strong> the <strong>POD</strong> now.</p>
<p>Sharing linke below : <a href="https://medium.com/@harsh.manvar111/resizing-pvc-disk-in-gke-c5b882c90f7b" rel="nofollow noreferrer">https://medium.com/@harsh.manvar111/resizing-pvc-disk-in-gke-c5b882c90f7b</a></p>
