Summary
The user is facing an issue where specific pods in the Airbyte deployment on AKS cluster are rebooting daily due to high CPU utilization. These pods were not present initially and appeared two weeks after deployment. The user is seeking assistance on how to resolve this issue.
Question
Hi Team,
We deployed Airbyte using helm chart latest available version on 24-June2024 - {0.220.2} in AKS cluster
Below mentioned pods are rebooting everyday.Upon checking logs using container insights i found always 100% cpu utilization for the pod, orchestrator-repl-job-36-attempt-19
These below mentioned pods we not see when we initially deployed airbyte helm chart. i see these pods from 2 weeks. Not sure how they came.
Could you please help me how to overcome this issue.
destination-mssql-write-36-19-ytidk
orchestrator-repl-job-36-attempt-19
source-marketo-read-36-19-cuvnh
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.