Based on the information provided in the extracts, it seems that the current Airbyte Helm chart does not support specifying a storage class for Minio. A user had a similar request and was advised to submit a feature request to the Airbyte GitHub repository. Here is the relevant extract: > User: hey, I’d like to specify storage class for the airbyte helm chart (for instance to use EFS CSI driver based storage class for minio) but it seems the chart does not support this. any chance that you will add it in the near future? or if you think I can add that config option as a PR > > Support: Hey there, please [submit this feature request to our github repo](https://github.com/airbytehq/airbyte/issues/new?assignees=&labels=type%2Fenhancement%2C+needs-triage&template=feature-request.md&title=) so it can be prioritized 🙂 If you're comfortable with it, you could also consider contributing to the project by adding this configuration option yourself as a Pull Request.

The error message you're seeing suggests that there are multiple default storage classes in your Kubernetes cluster. A Kubernetes cluster should only have one default storage class at a time. You can check your storage classes by running the following command:

bash kubectl get storageclass

This will list all the storage classes in your cluster. The default storage class will have

(default)

next to its name. If you see more than one storage class marked as default, you'll need to remove the default annotation from the extra ones. You can do this with the following command:

bash kubectl patch storageclass <your-storage-class> -p '{"metadata": {"annotations":{"<http://storageclass.kubernetes.io/is-default-class|storageclass.kubernetes.io/is-default-class>":"false"}}}'

Replace

<your-storage-class>

with the name of the storage class you want to remove as default. After running this command, only one storage class should be marked as default. You can then try to deploy Airbyte again. If you're still facing issues, it would be helpful to check the logs for any error messages. You can get the logs by running

kubectl logs <pod-name>

, replacing

<pod-name>

with the name of your Airbyte pod. For more detailed instructions, you can refer to the [Kubernetes documentation on storage classes](https://kubernetes.io/docs/concepts/storage/storage-classes/).

Sorry @Mayowa Ibitola, I seem to be having a bit of trouble. Don't worry though, I've pinged my support folks and they will try to fix me up! 🧑‍💻 Perhaps try again in 5mins?