Issue with setting JOB_MAIN_CONTAINER_MEMORY_REQUEST in Airbyte helm deployment on Kubernetes

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

Summary

The user is facing an issue related to setting memory and CPU requests in Airbyte helm deployment on Kubernetes, as described in the GitHub issue. The settings do not seem to have an effect on the destination or source pods.


Question

Hey Everyone,
I have a helm deployment of Airbyte on Kubernetes. The issue I am seeing is related to the issue stated here: https://github.com/airbytehq/airbyte/issues/35749 I have tried setting JOB_MAIN_CONTAINER_MEMORY_REQUEST and the equivalent one for CPU but it seems to have no effect on the destination-<XXX> or source-<XXX> pods
Any help would be appreciated. Thanks in advance


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

["helm-deployment", "airbyte", "kubernetes", "memory-request", "cpu-request", "pod"]