Summary
User is experiencing issues with the Airbyte Helm chart where resource limits and requests for the ‘container-orchestrator’ pod are not being updated as specified in the values.yaml file, leading to pods being stuck in PENDING state due to insufficient resources in the Kubernetes cluster.
Question
Hi!
I’m having some issues with the airbyte helm chart. I’m trying to edit the resource limits and requests for the “container-orchestrator” pod that spins up when starting a job. I’ve set the following values in values.yaml :
jobs:
resources:
requests:
memory: "1Gi"
cpu: "1000m"
limits:
memory: "2Gi"
cpu: "2000m"
worker:
resources:
requests:
memory: "1Gi"
cpu: "1000m"
limits:
memory: "2Gi"
cpu: "2000m"```
But as you can see in the screenshot, although environment variables are set to their correct values, the resource and request limits are not updated. This results in the pods being stuck in PENDING state due to lack of available resources in my kubernetes cluster.
Anybody have any ideas on how to solve this? Thanks in advance!
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1707910737276769) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
['airbyte', 'helm-chart', 'resource-limits', 'kubernetes', 'pending-state']
</sub>