Running Airbyte on a GKE autopilot cluster, deployed via helm with default values. Having an issue where the initial sync from MSSQL (CDC) to Bigquery (GCSStaging) fails multiple attempts. Logs look like everything is working fine, and then it just fails and starts another attempt. Some of the replicated tables are rather large 1M+ rows so I am wondering if the process is timing out before it can process all the data.

Based on the information provided in the extracts, it's possible that your sync operation might be timing out due to the large size of your tables. However, without the specific logs or error messages, it's hard to pinpoint the exact issue. In one of the [Slack conversations](https://airbytehq.slack.com/archives/C021JANJ6TY/p1669070432834879), a user faced a similar issue while moving a large amount of data from Google Bigquery to Google Firestore. The support team suggested that a timeout could be the issue and asked for the full logs and details about the system/Airbyte deployment. Also, in another [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1677596317798559), a user reported that their sync operation was taking a long time to complete when copying a small file from S3 to S3. The support team suggested upgrading to the latest version of the Helm Chart. As for running Airbyte on GKE Autopilot, there was a [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1665475892297689) where a user faced an issue and wondered if GKE Autopilot could be the cause. The support team mentioned that they hadn't seen anyone try Autopilot before and weren't sure if it could be the cause. To troubleshoot your issue, you might want to check the following: 1. Ensure that Airbyte has enough resources. You can refer to the [Airbyte scaling guide](https://docs.airbyte.com/operator-guides/scaling-airbyte/#on-kubernetes) for more information. 2. Try upgrading to the latest version of the Helm Chart. 3. Check the logs for any timeout errors or other issues. 4. If the issue persists, consider reaching out to the Airbyte community on [Slack](https://slack.airbyte.io/) or [creating an issue on GitHub](https://github.com/airbytehq/airbyte/issues/new?assignees=&labels=type%2Fbug&template=bug-report.md&title=). Please note that these are general suggestions based on the information available in the extracts. For a more accurate diagnosis, it would be helpful to have more specific details about your setup and the issue you're facing.