Deploy Kubernetes: Set resource limits for destination and source pods

[Rakhi_Modi]

• Is this your first time deploying Airbyte?: No / Yes
• OS Version / Instance: Ubuntu, Windows or MacOS… are some example remove it with yours
• Memory / Disk: you can use something like 4Gb / 1 Tb
• Deployment: Are you using Docker or Kubernetes deployment?
• Airbyte Version: What version are you using now?
• Source name/version:
• Destination name/version:
• Step: The issue is happening during sync, creating the connection or a new source?
• Description:

I have airbyte deployed on GKE cluster using helm chart.
The destination-snowflake-worker pod is consuming lot of resources
Limits:
cpu: 1500m
memory: 6Gi
Requests:
cpu: 1200m
memory: 4Gi

How can I modify it?
I have not specified these numbers in values.yaml or the environment variables.

[sajarin]

Hi @Rakhi_Modi, here’s a link to our documentation regarding setting resource limits on connector pods: https://docs.airbyte.com/deploying-airbyte/on-kubernetes/#setting-resource-limits. Let me know if it answers your question.

[jamesspout]

Hi @sajarin What does this look like for helm since what you’ve pointed to is for kustomize? I noticed that some of the jobs had absurdly high limits and it’s causing my pods to be stuck in init due to resource constraint.