Summary
Users are facing a timeout issue ‘Failed to copy files to CHECK pod’ in Airbyte while trying different versions. Looking for a solution as others are experiencing the same problem.
Question
Hi !
I tried a lot of versions for Airbyte now having always the issue Failed to copy files to CHECK pod
(meaning we go over the timeout of 60 seconds to copy files). <@U06Q3E1FGDQ> has the same issue. Anyone found the solution?
Our Kubernetes setup was working fine so far, now we are stuck and looking for alternatives…
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.
Join the conversation on Slack
["failed-to-copy-files", "timeout-issue", "kubernetes-setup", "alternative"]
Then I need to delete manually this
Same was working for months haha
At least we narrowed down where to look
This line but don’t know why it’s now an issue 
I mean any details 
Maybe something has changed with permissions, roles, bindings, etc. I had some glitches in the past with serviceaccount.
thank you for the clue, will look into this
Thanks <@U05JENRCF7C> and let me know if you got any more context Antoine!
Better let Airbyte create the service account ? <@U05JENRCF7C>
I got stuck here if I do, that’s why I started implementing cluster roles myself
I haven’t had any issues with values.yaml like this for several months now, and in my team, we performed several Airbyte upgrades in last few months
create: true```
It’s working -> don’t touch 
Deployed with
create: true```
Still the same issue to copy files in pod...
Any clue what could be the culprit, tried a lot of different Airbyte versions
All good in the end it seems to be due to our networking inside the cluster
Moved the deployment on a new nodepool with other machine type 
<@U01MMSDJGC9> if you ever see this haha 