Hi everyone, I’m trying to use a GCS bucket to store airbyte logs, I’ve no problem to deploy the app on GKE, but I don’t have any application logs, (files from Settings->Configuration-> Download Server Logs/Download Scheduler Logs are empty) Syncs are working but I’ve no logs, I can see the job history, but logs files are empty My configuration is: global.logs.storage.type: “GCS” global.logs.minio.enabled: “false” global.logs.externalMinio.enabled: “false” global.logs.s3.enabled: “false” global.logs.gcs.bucket: “my-bucket-name” global.logs.gcs.credentials: “path/to/my/secret” I already confirm that the secret is fine and the account has all the permission necessary to access and edit on the bucket. Is something missing in my configuration? Bucket is empty Thanks

Based on the information provided in the extracts, it seems like you have configured the GCS bucket correctly for logging. However, there are a few things you might want to check: 1. Ensure that the GCS bucket exists and is accessible. Although you mentioned that the account has all the necessary permissions, it might be worth double-checking. 2. Check if there are any issues with the GCS bucket itself. In one of the [Slack conversations](https://airbytehq.slack.com/archives/C021JANJ6TY/p1665475892297689), a user encountered a

NoSuchBucket

exception even though the bucket existed. 3. There might be a bug with Airbyte when using a certain percentage of Airbyte minio’s storage and then connecting with GCS. This was mentioned in a [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1670843029092339). 4. There could be an issue with the version of Airbyte you are using. In a [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1674160309884009), a user faced an issue with Airbyte version 0.40.26 on Kubernetes (GKE) which prevented the airbyte-worker from launching new pods. Downgrading to version 0.40.25 resolved the issue. If you've checked all of these and are still facing the issue, it might be a good idea to reach out to the Airbyte community on their [Slack channel](https://airbytehq.slack.com/archives/C021JANJ6TY) or [forum](https://discuss.airbyte.io) for further assistance.

one way you can try to debug this daniel is exec’ing into the pod and seeing if you can authenticate to the bucket through manual means to ensure it’s not a network related issue

Hi Conor, I already did it and it works, that way I tested network and secret at the same time