Hey Team, I'm running Airbyte on EKS and 3 pods keep running into Pending state with the same Event,

Warning  FailedScheduling  35s   default-scheduler  0/1 nodes are available: 1 node(s) had volume node affinity conflict.

It gets fixed when I resize the

airbyte-volume-configs

persistent volume. Initially from 500Mi to 2Gi and then later pulled it to 20Gi too. Still facing this issue. Is there a suggestive volume that needs to be configured? Or is there a way to reclaim the volume if this is temporary? https://discuss.airbyte.io/t/eks-pods-running-into-pending-state-due-to-pv/3211

The issue is the affinity conflict. Something afaik that is AWS specific. Basically, each AWS region has a few Availability zones. EC2 instances usually are just assigned a region, so the AZ it's in is not certain (I'm pretty sure this is true, at least it was for me and my limited understanding of things). Sometimes the AZ doesn't match the original AZ that the volume was created in, so you have an affinity conflict. There are two ways to solve this that I know of. 1. Make sure you're running at least one instance in each AZ. The easiest way is to set the min_size on the autoscaling group for the instance to the amount of AZs in the region you're using. 2. Replace postgres and minio with RDS and S3, so you don't need to have Persistent Volumes anymore. Then you don't have to worry about that at all. Hopefully this helps!

Hello Mukul Gopinath, it's been a while without an update from us. Are you still having problems or did you find a solution?