CPU and Memory Limits Discrepancies in Airbyte EKS Deployment


User is experiencing discrepancies in CPU and memory limits and requests in Airbyte EKS deployment despite updating resource_requirements in the actor_definition table. They are seeking advice on resolving the issue.


Hello Team,
I have updated resource_requirements in the actor_definition table with cpu and memory limits and requests, However, i am still seeing discrepancies in the logs regarding the cpu and memory requests and limits. I also confirmed resource_requirements in the connection table is null hence that could not be interfering with this config. I have airbyte deployed on EKS and version of airbyte being used is: 0.50.31. Can someone tell me if there is something else we can do to use the cpu requests and limits.?

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

["cpu-limits", "memory-limits", "actor-definition-table", "connection-table", "airbyte-eks", "resource-requirements"]