Hello Team, I am trying to deploy Airbyte on a K8s...
# replication-troubleshooting
d
Hello Team, I am trying to deploy Airbyte on a K8s using helm (all defaults, no custom values), and I am getting an error
Error: failed pre-install: timed out waiting for the condition
. If I list all resources created in the namespace, I can see that the pod
pod/airbyte-airbyte-bootloader
is running, and 2 other pods (
pod/airbyte-db-0
and
pod/airbyte-minio-0
) are pending which seems to be an issue with `PersistentVolumeClaims`:
Copy code
Type     Reason             Age                   From                Message
  ----     ------             ----                  ----                -------
  Normal   NotTriggerScaleUp  3m32s (x21 over 23m)  cluster-autoscaler  pod didn't trigger scale-up: 2 pod has unbound immediate PersistentVolumeClaims
  Warning  FailedScheduling   37s (x25 over 24m)    default-scheduler   0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
Anybody had a similar problem? Any ideas how to fix it?
j
Did you check your PVCs? and which k8s provider are you using?
e
Are you running on EKS fargate? As far as I know with default values it doesn't work there. Because they don't support persistent volumes I think... I at least had some trouble.
d
Thank you for your feedback I use DigitalOcean as my k8s provider. I have already some pods that requested PV before and they were created successfully.