Summary
The orchestrator-repl pod is throwing an error during a MySQL to S3 sync operation on a Kubernetes deployment using Helm chart v0.50.35. The issue seems related to service account permissions and log publishing.
Question
Hello! We have installed airbyte on Kubernetes, using the helmchart v0.50.35. All was running fine, but when we trigger a sync mysql -> s3, the pod orchestrator-repl is throwing an error. Despite we set the service account and even AWS keys on the connector through UI. It’s like the orchestrator is just ignoring the service account that is already working on the rest of the stack. I think, from the attached logs, the orchestrator is not been able to publish the logs. Please advise.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.