Adjusting CPU allocation for container in Airbyte destination pod on Kubernetes

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

When running Airbyte OSS on Kubernetes via the official Helm chart, a destination pod with five containers is started. One of the containers, remote-stdin, is requesting an inappropriate amount of CPU. The user is looking for a way to edit this CPU allocation value via the values.yaml file.


Question

Hello,

I am running airbyte OSS on kubernetes via the official helm chart. When running a sync, a destination pod with five containers is started. One of the containers, remote-stdin is requesting an inappropriate amount of cpu. I can’t find a way to edit this value via the values.yaml. Does anybody know of a way to set it?


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

["airbyte-oss", "kubernetes", "helm-chart", "cpu-allocation", "values.yaml", "destination-pod", "container"]
2

I also started a github issue: https://github.com/airbytehq/airbyte/issues/35749

3

I Asked a similar question the other day and didn’t get an answer yet. I’m running airbyte in Azure Kubernetes, so I just allowed it to auto-scale another node whenever it needs to (which is every sync) as a workaround for now. It looks like it uses ~ half of the resources it requests, so maybe they’re trying to play it safe and ensure the pod isn’t killed prematurely