@kapa.ai My sources and destinations connect perfectly, but no source of any kind is fethcing and writing the rows. Something appears to be misconfigured. I am using Digital Ocean with Kubernetes.

Based on the knowledge sources, there are a few potential issues to consider when using Airbyte on Digital Ocean with Kubernetes, especially if sources and destinations connect but no data is being fetched or written: 1. Digital Ocean Managed Databases: If you are using Digital Ocean's managed MySQL, by default, the binary logs are periodically cleared outside of the MySQL server's replication settings. This can interfere with Change Data Capture (CDC) replication. You may need to contact Digital Ocean support to disable this feature if you want to use CDC replication with Airbyte. For other databases, similar managed service limitations may apply, so check the specific documentation for your source type [Troubleshooting MySQL Sources](https://docs.airbyte.com/integrations/sources/mysql/mysql-troubleshooting#troubleshooting-mysql-sources). 2. Schema Fetching Issues: There are reports of Airbyte failing to fetch schemas from Digital Ocean managed MongoDB, even when the network setup is correct. This could be due to compatibility or configuration issues with managed services on Digital Ocean. Review your connector logs for more details, as the error may be related to how the managed service is configured or how Airbyte is connecting to it [Source MongoDB - Failed to fetch MongoDB of DigitalOcean Managed DB Schema](https://discuss.airbyte.io/t/1931). 3. Kubernetes Environment Variables and Secrets: When running Airbyte on Kubernetes, ensure that all necessary environment variables and secrets (such as access keys for object storage or database credentials) are correctly set in your deployment. There are cases where missing environment variables in certain containers (like the init or main container) can cause failures in source or destination operations [Airbyte 1.2.0 on Kubernetes/EKS: Cannot create new sources as "Test the Source" fails with HTTP 500](https://github.com/airbytehq/airbyte/issues/48809). 4. Pod and Resource Issues: If pods (source, destination, or orchestrator) are stuck in a terminating state or not starting correctly, this can prevent syncs from running. This may be due to resource constraints, misconfiguration, or issues with Kubernetes itself. Check the pod status and logs for errors, and ensure your cluster has enough resources [Destination, orchestrator, and source pod all stuck in terminating](https://discuss.airbyte.io/t/2545). 5. General Misconfiguration: Double-check your Airbyte connection and sync configurations, including network policies, firewall rules, and Kubernetes service definitions, to ensure that all components can communicate as expected. If you have checked all of the above and the issue persists, reviewing the Airbyte logs for your sync jobs and connector pods will provide more specific error messages that can help pinpoint the misconfiguration. If you can provide more details about your source type and any error logs, I can help further narrow down the issue.