In Airbyte OSS v0.57.3, what environment variables are needed to connect to Minio for logging?

To connect to Minio for logging in Airbyte OSS v0.57.3, you need to configure several environment variables. Based on the provided knowledge sources, here are the relevant environment variables: 1. Minio Configuration: - `logs.externalMinio.enabled`: Switch to enable or disable an external Minio instance. - `logs.externalMinio.host`: External Minio Host. - `logs.externalMinio.port`: External Minio Port. - `logs.externalMinio.endpoint`: Fully qualified hostname for S3-compatible storage. 2. S3 Configuration (if using S3-compatible storage): - `logs.s3.enabled`: Switch to enable or disable custom S3 Log location. - `logs.s3.bucket`: Bucket name where logs should be stored. - `logs.s3.bucketRegion`: Region of the bucket (must be empty if using Minio). Here is an example configuration:

yaml logs:   externalMinio:     enabled: true     host: your-minio-host     port: 9000     endpoint: <http://your-minio-endpoint>   s3:     enabled: false     bucket: your-s3-bucket     bucketRegion: ""

Additionally, you might need to set the following environment variables in your deployment configuration:

yaml extraEnv:   - name: S3_MINIO_ENDPOINT     value: "<http://your-minio-endpoint>"   - name: AWS_ACCESS_KEY_ID     value: "your-minio-access-key"   - name: AWS_SECRET_ACCESS_KEY     value: "your-minio-secret-key"

For more detailed information, you can refer to the [Airbyte documentation on Kubernetes deployment](https://docs.airbyte.com/deploying-airbyte/on-kubernetes#configure-logs). References: - [Forum Post: Worker process of Airbyte > v0.40.9 fails to start on custom S3 config](https://discuss.airbyte.io/t/2849) - [Forum Post: Invalid Access Key for Source Connecter s3](https://discuss.airbyte.io/t/1669)

@kapa.ai Is external Minio no longer supported in v0.57.3?

Based on the information provided in the knowledge sources, it appears that there have been issues and ongoing work related to using external Minio with Airbyte's Helm charts. Specifically: 1. Issue #36826 mentions that a user was successfully using an external Minio with Helm Chart version 0.53.313 but faced issues when upgrading to version 0.64.0. The property

global.logs.minio.enabled

was still in the configuration but was deemed useless ([source](https://github.com/airbytehq/airbyte/issues/36826)). 2. Issue #34512 indicates that users faced sync errors when using external Minio with Helm Chart version 0.50.44. The error was related to the

S3_LOG_BUCKET_REGION

environment variable, and users had to add

global.logs.s3.bucketRegion

to their

values.yaml

to resolve it ([source](https://github.com/airbytehq/airbyte/issues/34512)). 3. Issue #34539 suggests using the default Minio for now, as there is ongoing work to improve the existing chart ([source](https://github.com/airbytehq/airbyte/issues/34539)). Given these points, it seems that while external Minio might still be configurable, there have been significant issues and changes in the Helm charts that could affect its functionality. The recommendation from the development team is to use the default Minio for now due to ongoing improvements. Therefore, it is not explicitly stated that external Minio is no longer supported in version 0.57.3, but there are known issues and limitations that might make it challenging to use. For the most reliable setup, it is advisable to follow the latest recommendations and possibly use the default Minio until the improvements are released. For more detailed and up-to-date information, you might want to follow the related issues on GitHub: - [Issue #36826](https://github.com/airbytehq/airbyte/issues/36826) - [Issue #34512](https://github.com/airbytehq/airbyte/issues/34512) - [Issue #34539](https://github.com/airbytehq/airbyte/issues/34539)