My

airbyte-minio-0

pod is sometimes failing with exit code 137 (OOM error). I'd like to increase the resources, but that is not possible in the Helm chart because they are hardcoded. Why is that the case?

The issue you're experiencing with the

airbyte-minio-0

pod failing with exit code 137 (indicating an Out of Memory error) is related to the fact that the resources for Minio in the Airbyte Helm chart are hardcoded and cannot be disabled or configured easily. This has been a known issue as highlighted in the following GitHub issue: > Since [this pull request](https://github.com/airbytehq/airbyte/pull/16131), there is a new set of Minio resources in the main Airbyte Helm chart that: > - Can't be disabled, they are always deployed - this causes conflicts with the Bitnami Minio chart. > - Aren't suitably configurable to be used as a replacement for the Bitnami Minio chart, e.g., I need to set annotations on the Minio Service, which the Bitnami chart supports but the new resources don't. The expected behavior is that you should be able to choose whether to run the Bitnami Minio chart or the bundled Minio deployment to avoid conflicts and allow for better configurability. However, the current implementation does not support this flexibility. For more details, you can refer to the original GitHub issue [here](https://github.com/airbytehq/airbyte/issues/16586). If you are willing to contribute, you might consider submitting a pull request to make these resources configurable. Otherwise, you may need to wait for an update from the Airbyte team that addresses this limitation. If you need further assistance or have more questions, feel free to ask!