David Robinson
11/26/2025, 12:41 PMkapa.ai
11/26/2025, 12:42 PMJOB_MAIN_CONTAINER_MEMORY_REQUEST and JOB_MAIN_CONTAINER_MEMORY_LIMIT environment variables. These variables define the minimum and maximum RAM usage for job containers, including the orchestrator pod, and are applicable to both Docker and Kubernetes deployments. The units should follow Docker or Kubernetes conventions (e.g., 2g for 2 gigabytes, 2048Mi for 2048 mebibytes). Example for Docker Compose or .env file: JOB_MAIN_CONTAINER_MEMORY_REQUEST=2g JOB_MAIN_CONTAINER_MEMORY_LIMIT=2g Example for Kubernetes (values.yaml): yaml global: jobs: resources: requests: memory: 2Gi limits: memory: 2Gi Setting these variables ensures that the orchestrator and other job containers have the appropriate memory allocated to them. Note that these settings apply to all job containers, including orchestrator, read, and write pods, as they all derive their resource requirements from these environment variables. More granular control (e.g., different settings for orchestrator vs. read/write) is not available via these variables alone, but can be achieved through connector or connection-specific resource requirements in the database if needed [Orchestrator container gets same resource limit/request values as read/write containers](https://discuss.airbyte.io/t/3775) [Configuring Connector Resources](https://docs.airbyte.com/platform/1.8/operator-guides/configuring-connector-resources).David Robinson
11/26/2025, 1:29 PMkapa.ai
11/26/2025, 1:29 PMkapa.ai
11/26/2025, 1:29 PM