@kapa.ai I am getting below error Warning from source: Workload failed, source: workload-monitor-heartbeat See less Airbyte could not track the sync progress. Sync process exited without reporting status. I am facing error and threre are no logs getting displayed for jobs. I want to know if this is becuase of logs storage issue, I am having internal minio as logs storage Warning from source: Workload failed, source: workload-monitor-heartbeat See less Airbyte could not track the sync progress. Sync process exited without reporting status. I running my workloads with Airbyte Community Version(1.4.0) My all(36) connection syncs both(MongoDB -> Postgres, Postgres -> Postgres) started failing. I am running the Airbyte on EKS with 3 nodes(m5.2xlarge), I have stopped the all connection syncs and started just one connection again manually, only the source-postgres-check pod is getting completed, other subsequent pods destionation-postgres-check and replication-job have not been launched, not sure if this is because of resources.

Based on the information provided in the knowledge sources, I can offer some insights into your issue, although the exact cause is not definitively stated in the available documents. The error you're experiencing, particularly the lack of logs and the "Workload failed, source: workload-monitor-heartbeat" message, could be related to several issues that have been reported in similar Airbyte deployments on Kubernetes: 1. Storage Issues: You mentioned using internal Minio for log storage. This could indeed be a factor. According to a similar issue discussed in [Forum Post: K8s No logs available](https://discuss.airbyte.io/t/1078), increasing the space for Minio at the

/storage

path was suggested as a solution. 2. Resource Constraints: Given that you're running on EKS with 3 m5.2xlarge nodes and experiencing issues with pod creation after the source-postgres-check, it's possible that you're hitting resource limits. This aligns with observations in [Github Issue: Airbyte OSS via Helm on EKS: sync jobs are failing constantly](https://github.com/airbytehq/airbyte/issues/35346), where sync jobs were failing due to timeouts in pod creation. 3. Worker Pod Issues: There's a possibility that failed jobs are not releasing resources properly. As mentioned in a comment on [Github Issue: Airbyte is not stable in k8s env](https://github.com/airbytehq/airbyte/issues/38853), restarting the worker pod sometimes helps resolve sync job failures. 4. Version-specific Issues: You're using Airbyte Community Version 1.4.0, which is more recent than the versions mentioned in the knowledge sources. There could be version-specific issues that are not covered in the provided information. To troubleshoot: 1. Check your Minio storage capacity and increase it if necessary. 2. Monitor your cluster's resource usage to ensure you're not hitting limits. 3. Try restarting the Airbyte worker pods to see if it resolves the issue. 4. If possible, check the Kubernetes events and logs for the namespace where Airbyte is deployed for any resource constraint or scheduling issues. If these steps don't resolve the issue, you may need to open a new issue on the Airbyte GitHub repository or seek support through their community channels, as the exact problem you're facing isn't fully covered in the provided knowledge sources.