Deploying Airbyte with Existing MinIO Cluster

Slack Knowledge Base Q&A API, Terraform and Other Topics
, , , ,
1

Summary

User inquires about deploying Airbyte on Kubernetes while leveraging an existing MinIO cluster instead of the default MinIO StatefulSet created by the Airbyte Helm chart.


Question

Hi team, as I know that there is something changed in bitnami minio helm chart so that it has been replaced with your own one. I’m trying to deploy airbyte on k8s and it seems to create minio statefulset directly when the global.storage.type is set to minio. Is there any way to leverage my existing minio cluster?

apiVersion: apps/v1 #  for k8s versions before 1.9.0 use apps/v1beta2  and before 1.8.0 use extensions/v1beta1
kind: StatefulSet
metadata:
  # This name uniquely identifies the Deployment
  name: airbyte-minio
...
{{- end }}```

<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/p1709999013424239) if you want
to access the original thread.

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

<sub>
['minio', 'helm-chart', 'kubernetes', 'statefulset', 'airbyte']
</sub>