Hey all, we have been working to create a full GCP Terraform deployment of all components to form a full Airbyte stack: • Airbyte GKE Cluster • Airflow (Composer 2) • Cloud SQL (PostreSQL) • Cloud Storage • VPC & Firewall rules to support We had two issues come up we hope there might be some insight into. 1. When disabling Minio in the helm chart after defining a Cloud Storage destination, logs will not write to storage. a. After enabling Minio with the GCS setup logs are going to GCS 2. Helm Chart versioning is not being incremented with Airbyte versioning. a. This shows on line 18 the helm chart version, and on line 24 the app version. https://github.com/airbytehq/airbyte/blob/master/charts/airbyte/Chart.yaml#L15-L18 b. In our case the 'appVersion' was incremented without carrying forward a new helm chart version as well. Even on line 15 it says "This version number should be incremented each time you make changes to the chart and its templates, including the app version." - this was not done. i. This causes problems when you want to define in the Terraform build the deployment you're going after, as you'd need to push a new helm chart version to pick up the new appVersion. I've been accustomed to submitting github issues, should I do the same for these?

Hi Zach! Could you deploy this helm chart and setup a connection? I still can deploy on kubernetes but something wrong is happening that when i try to create a new connection it throws the fallowing error:

The connection tests failed.

Internal Server Error: The Access Key Id you provided does not exist in our records. (Service: S3, Status Code: 403, Request ID: 16FBA5BD9BF3F037, Extended Request ID: null)

i am using the default config..