Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> how do I increase the memory limit of an Airbyte cluster configured with abctl (local install) as jobs -&gt; resources -&gt; limits -&gt; memory is set to 4Gi and I need it be 6

There is some uncertainty here because `abctl` local installs currently have issues propagating `global.jobs.resources` from `values.yaml` to the actual job pods, so simply changing that value may not take effect. [<https://github.com/airbytehq/airbyte/issues/73346|Resource limits bug>]
You have two main options, both requiring a reinstall or upgrade with updated values:
*1. Try via `values.yaml` (may be affected by the bug)*
In your `values.yaml` used with `abctl local install`, set:
```global:
  jobs:
    resources:
      requests:
        cpu: "2"        # example
        memory: 4Gi     # example
      limits:
        cpu: "4"        # example
        memory: 6Gi     # <- change from 4Gi to 6Gi
```
Then reinstall/upgrade with:
```abctl local install --values values.yaml
```
This is the intended way, but the open issue shows that in some `abctl` versions these values may be ignored. [<https://github.com/airbytehq/airbyte/issues/73346|Resource limits bug>]
*2. Set env vars directly on `workload-launcher` (recommended workaround)*
As a workaround confirmed in the issue, set the job resource limits via environment variables on the `workload-launcher` deployment in your `values.yaml`:
```workloadLauncher:
  extraEnv:
    - name: JOB_MAIN_CONTAINER_CPU_LIMIT
      value: "4"        # example
    - name: JOB_MAIN_CONTAINER_CPU_REQUEST
      value: "2"        # example
    - name: JOB_MAIN_CONTAINER_MEMORY_LIMIT
      value: "6Gi"      # <- set to 6Gi here
    - name: JOB_MAIN_CONTAINER_MEMORY_REQUEST
      value: "4Gi"      # example
```
Reinstall/upgrade with:
```abctl local install --values values.yaml
```
Then verify the env vars are present:
```kubectl exec -n airbyte deploy/airbyte-abctl-workload-launcher -- env | grep JOB_MAIN
```
These env vars control the default CPU/memory requests/limits for job containers (source/destination pods). [<https://docs.airbyte.com/platform/1.6/operator-guides/configuring-connector-resources|Configuring resources>; <https://github.com/airbytehq/airbyte/issues/72457|HANA workaround>] :thumbsup: 0 button :thumbsdown: 0 button :information_source: *Tip:* Mention *@kapa.ai* in the thread for follow-ups or *DM the app* for *1-to-1* help.

<@U04S8PLJWMT> I don't have a values.yaml - do I just create one?

Yes. For `abctl` installs you’re expected to create your own `values.yaml` override file and pass it to the install command.
The docs describe this pattern: you don’t copy the whole chart `values.yaml`, you just create a minimal `values.yaml` with the overrides you need. [<https://docs.airbyte.com/platform/2.0/deploying-airbyte#3-create-a-valuesyaml-override-file|Create values.yaml 2.0>]
Example minimal `values.yaml` you can create:
```workloadLauncher:
  extraEnv:
    - name: JOB_MAIN_CONTAINER_MEMORY_LIMIT
      value: "6Gi"
    - name: JOB_MAIN_CONTAINER_MEMORY_REQUEST
      value: "4Gi"
```
Then install/upgrade with that file, e.g.:
```abctl local install --values values.yaml
```
This follows the documented “create a values.yaml override file” approach used for Helm-based installs. [<https://docs.airbyte.com/platform/deploying-airbyte#3-create-a-valuesyaml-override-file|Create values.yaml>] :thumbsup: 0 button :thumbsdown: 0 button :information_source: *Tip:* Mention *@kapa.ai* in the thread for follow-ups or *DM the app* for *1-to-1* help.