<p>I have a bare-metal kubernetes cluster. I'm trying to understand why the claim is not binding to the volume, and i don't understand.</p>
<p>This is the volume:</p>
<pre><code>apiVersion: v1
kind: PersistentVolume
metadata:
  name: main-pv
spec:
  capacity:
    storage: 1Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Delete
  local:
    path: /data/mongodb
  nodeAffinity:
    required:
      nodeSelectorTerms:
        - matchExpressions:
            - key: kubernetes.io/hostname
              operator: In
              values:
                - ip-172-31-68-214
</code></pre>
<p>this is what I see in describe pvc:</p>
<pre><code>Name:          xxxx-services-1-mongodb
Namespace:     default
StorageClass:
Status:        Pending
Volume:
Labels:        app.kubernetes.io/component=mongodb
               app.kubernetes.io/instance=xxxx-services-1
               app.kubernetes.io/managed-by=Helm
               app.kubernetes.io/name=mongodb
               helm.sh/chart=mongodb-9.1.1
Annotations:   meta.helm.sh/release-name: xxxx-services-1
               meta.helm.sh/release-namespace: default
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Mounted By:    xxxx-services-1-mongodb-5547c455ff-mhznt
Events:
  Type    Reason         Age                From                         Message
  ----    ------         ----               ----                         -------
  Normal  FailedBinding  3s (x62 over 15m)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set
</code></pre>

<p>I found out the issue: there a requirement for 8Gi capacity. I thought that it will be described in <code>describe pvc</code> but no, only in the yaml...</p>
