Yes, this appears to be a known issue with Airbyte running in Kubernetes environments. Based on the information provided in the knowledge sources, there are several reports of sync jobs hanging or getting stuck for extended periods without creating pods. This problem has been reported in multiple sources: 1. [Forum Post: All syncs hanging for days](
https://discuss.airbyte.io/t/1916) describes a situation where multiple connections were stuck in the 'Running' state for days, though nothing was actually being synced. 2. [Github Issue: Sync job hangs for days](
https://github.com/airbytehq/airbyte/issues/38345) reports sync jobs hanging for days without restarting or failing. 3. [Forum Post: Temporal Scheduler Causing Multiple Syncs to Hang](
https://discuss.airbyte.io/t/1293) mentions syncs getting hung up and running for much longer than expected. The root cause of this issue isn't clearly identified in the provided sources, but it seems to be related to problems with pod creation, scheduling, or cleanup in Kubernetes environments. Some possible factors mentioned include: - Issues with the Temporal scheduler - Problems with pod garbage collection - Failures in creating pods for read or write steps It's worth noting that in some cases, restarting worker pods or manually cancelling the hanging syncs has been reported to temporarily resolve the issue. To troubleshoot and potentially resolve this problem, you might want to: 1. Check the logs of your Airbyte server and worker pods for any relevant error messages. 2. Consider upgrading to the latest version of Airbyte, as some issues may have been resolved in newer releases. 3. Review your Kubernetes cluster's resources and configuration to ensure there are no constraints preventing pod creation. If the problem persists, it would be advisable to report this issue to the Airbyte community or support channels with detailed logs and your specific setup information.