Issue with resource_requirements in actor_definition on EKS

Summary

In Airbyte version 0.57.3 deployed on EKS, pods are not recognizing the resource_requirements specified in actor_definition, while connection-level resource configuration is functioning correctly. The connector-level resource_requirements are visible via the get_source_definition API endpoint.


Question

In version 0.57.3 deployed on EKS, we are unable to get pods to pick up resource_requirements set in actor_definition however, the connection level resource config is working. Also we are able to see the connector level resource_requirements when calling the get_source_definition api endpoint



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

['resource-requirements', 'actor-definition', 'eks', 'get-source-definition', 'airbyte-0.57.3']