PersistentVolumeClaims not available issue with Airbyte setup on Kubernetes

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user is facing an issue with PersistentVolumeClaims not being available when setting up Airbyte on Kubernetes. The problem seems to be related to a missing storageClassName in the spec configuration.


Question

I am using kubernetes setup & are trying to use external postgres db setup. I keep running into a PersistentVolumeClaims not being available issue.

helm install airbyte airbyte/airbyte --namespace airbyte --values ./values.yaml
on StatefulSet/airbyte-minio
0/7 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/7 nodes are available: 7 Preemption is not helpful for scheduling.
I’ve checked & kubectl get sts -n airbyte airbyte-minio -oyaml

I noticed my spec is missing a storageClassName

      storageClassName: gp2```
I have updated the class manually & restarted it. This resolved this issue, however not a real solution.

I've tried adding this to my values.yaml file as such

```airbyte:
  minio:
    persistence:
      enabled: true
      storageClassName: gp2
      size: 500Mi```
without luck either

`kubectl get storageclass`
```NAME   PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
gp2    <http://kubernetes.io/aws-ebs|kubernetes.io/aws-ebs>   Delete          WaitForFirstConsumer   false                  28h```


<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1729810104187299) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["kubernetes-setup", "external-postgres-db", "persistentvolumeclaims", "airbyte-setup", "storageclassname", "values.yaml", "statefulset", "minio", "persistence", "storageclass"]
</sub>
2

after exploring the chart file I also tried setting up the values.yaml with the following with the same issue

  storage:
    volumeClaimValue: "500Mi"
    storageClassName: "gp2"```