When deploying airbyte on kubernetes (non-managed), there aren't any persistent volumes being created, but there are persistent volume claims. Am I missing a step?

airbyte-bootloader-6f9qw              1/1     Running            0              44m
airbyte-cron-6d96cc88bf-2n7rv         0/1     Pending            0              44m
airbyte-db-57c84b5d69-48cv6           0/1     Pending            0              44m
airbyte-minio-fbccbf969-r9flz         0/1     Pending            0              44m
airbyte-pod-sweeper-9cd5d7c8b-85z4p   1/1     Running            0              44m
airbyte-server-55d4479c47-kzptn       0/1     Pending            0              44m
airbyte-temporal-58bbb9fb49-gx5gm     1/1     Running            0              44m
airbyte-webapp-9c5498c47-bgm8r        1/1     Running            0              44m
airbyte-worker-5d495ffc7d-zj5ng       0/1     CrashLoopBackOff   13 (84s ago)   44m

The worker pod is a crashloop waiting on the db pod, but the db pod is waiting for the pvc which doesn't have a persistent volume to claim. PVCs:

Name:          airbyte-minio-pv-claim
Namespace:     default
StorageClass:
Status:        Pending
Volume:
Labels:        app=airbyte-minio-storage-claim
Annotations:   <none>
Finalizers:    [<http://kubernetes.io/pvc-protection|kubernetes.io/pvc-protection>]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       airbyte-minio-fbccbf969-r9flz
Events:
  Type    Reason         Age                   From                         Message
  ----    ------         ----                  ----                         -------
  Normal  FailedBinding  18s (x662 over 165m)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set


Name:          airbyte-volume-configs
Namespace:     default
StorageClass:
Status:        Pending
Volume:
Labels:        airbyte=volume-configs
Annotations:   <none>
Finalizers:    [<http://kubernetes.io/pvc-protection|kubernetes.io/pvc-protection>]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       airbyte-cron-6d96cc88bf-2n7rv
               airbyte-server-55d4479c47-kzptn
Events:
  Type    Reason         Age                   From                         Message
  ----    ------         ----                  ----                         -------
  Normal  FailedBinding  18s (x662 over 165m)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set


Name:          airbyte-volume-db
Namespace:     default
StorageClass:
Status:        Pending
Volume:
Labels:        airbyte=volume-db
Annotations:   <none>
Finalizers:    [<http://kubernetes.io/pvc-protection|kubernetes.io/pvc-protection>]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       airbyte-db-57c84b5d69-48cv6
Events:
  Type    Reason         Age                   From                         Message
  ----    ------         ----                  ----                         -------
  Normal  FailedBinding  33s (x661 over 165m)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set

Hey @Callum McCaffery are you deploying with kustomize?

Hey @Sunny Hashmi (Airbyte), I'm deploying using kube/overlay/stable using kubectl