Adjusting Airbyte database size on Kubernetes cluster

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

Summary

When trying to implement Airbyte on a Kubernetes cluster with a restriction on persistent volume size, the user is facing issues with the default size of the Airbyte database. They have tried updating the volumeClaim in values.yaml but the database still uses the default 500Mi size. They are seeking advice on how to make the necessary changes for Airbyte to function properly.


Question

Hi everyone, I wanted to implement airbyte on kubernetes cluster, our kubernetes cluster restrict the creation of pv less than 500Mi and I updated the volumeClaim in values.yaml and increase the size but unfortunately the airbyte-db use the 500Mi and I coudn’t change the default value. Do you have any idea to make some changes to work properly? Thanks in advance


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["airbyte", "kubernetes-cluster", "pv", "volumeclaim", "database-size"]
2

Few ideas, feel free to pick any:

  1. contribute to project, https://github.com/airbytehq/airbyte-platform/blob/aeda63e9de2d60573888f4f4982aa2e76765699e/charts/airbyte/templates/airbyte-db.yaml#L84|airbyte-db.yaml#L84 could have similar option as https://github.com/airbytehq/airbyte-platform/blob/aeda63e9de2d60573888f4f4982aa2e76765699e/charts/airbyte/templates/minio.yaml#L24|minio.yaml#L24
  2. use external database
  3. create custom helm chart