Multiple pv and pvc for different GKE deployments

General Discussions
1

I am trying to create multiple pv and pvc with gce-pd for multiple different deployments

Cluster information:

Kubernetes version:
Client Version: v1.26.0
Kustomize Version: v4.5.7
Server Version: v1.24.9-gke.3200

Cloud being used: GKE
Installation method:
Host OS: ubuntu 20.04
CNI and version:
CRI and version:
Presently i have two (pv+pvc) first one is functioning perfectly newly created is not functioning
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
bfk-storage 420Gi RWO Retain Bound default/bfk-storage-claim standard 25h
statemine-storage 200Gi RWX Retain Bound default/statemine-storage-claim standard 41m
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
bfk-storage-claim Bound bfk-storage 420Gi RWO standard 25h
statemine-storage-claim Bound statemine-storage 200Gi RWX standard 41m
not able to exec into the pod created with the second one
Error Message:
error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec “5b4218b9e22a136753dc84f6b2bcde9726b0f2bfdd56e3e739d019fc9c0e234b”: OCI runtime exec failed: write /tmp/runc-process100307311: no space left on device: unknown

2

I recommend using the markdown for code snippets when copy/pasting plain text. The formatting gets lost without it.

This leads me to assume you lack disk space for your containers. How big are your container images?

3

Thank you for the response. Image size is around 2.53GB

4

I think you need to login to the cloud server and treat it like an out of storage issue. Track down why you have no space left. Commands in linux to help with this are df and du. You can start with df -h but du requires some Linux know how and intuition. read the man page for that one. I tend to use these flags as I drill down du -shx /path/i/suspect --max-depth 3.