I am trying to trigger airbyte (hosted on a GCP VM) sync from a DAG in Cloud Composer. The connection to airbyte VM is failing (connection timeout error).

Based on the information provided in the knowledge sources, it seems like you might be facing a network issue between your Cloud Composer and Airbyte server. One of the [forum posts](https://discuss.airbyte.io/t/1070) suggests that you need to allow Airflow Composer to connect to your Airbyte server by changing the network settings between both instances. However, if you are using Composer v2 with autoscaling, the workers are created dynamically and don’t have fixed IP. This could be the reason why you are not able to see their IP and whitelist them to access your Airbyte server. Unfortunately, the knowledge sources do not provide a solution to this specific issue. In case of connection timeout errors, it might be helpful to increase the timeout settings. For instance, in an [Airflow DAG example](https://docs.airbyte.com/operator-guides/using-the-airflow-airbyte-operator#creating-a-simple-airflow-dag-to-run-an-airbyte-sync-job), the

timeout

parameter is set to

3600

seconds. You might want to adjust this value based on your requirements. If the issue persists, it would be beneficial to check the resource configuration of your instance as suggested in one of the [Github discussions](https://github.com/airbytehq/airbyte/discussions/34577). The HikariPool warnings could be a symptom of an overloaded system or resource constraints that affect the application's performance. Please note that these are just suggestions based on the information available in the knowledge sources and might not directly solve your issue. It would be best to reach out to the Airbyte or Google Cloud support for more specific assistance.