Hey team. wondering if you could help with this issue. Here is the ai chat i perviously had Subject: abctl v0.30.4 + Airbyte 2.1.0 —

--low-resource-mode

toggle breaks install, MinIO missing Environment: • Airbyte: 2.1.0 (self-hosted, single-node kind on EC2) • abctl: v0.30.4 • Helm chart: V2 (default) What happened: Originally installed without

--low-resource-mode

, then re-ran with the flag. This triggered a known Helm patch ordering bug (duplicate

..._REQUEST

entries with both

value:0

and

valueFrom

in the configmap patch list). Now every

abctl local install

— with or without the flag — fails at ~23s before pods start. Error:

unable to install helm: failed to create patch: The order in patch list:
[map[name:CHECK_JOB_MAIN_CONTAINER_CPU_REQUEST value:0] ... map[name:CHECK_JOB_MAIN_CONTAINER_MEMORY_REQUEST valueFrom:...]]
doesn't match $setElementOrder list: [...]

What's been tried: • Re-running install with/without

--low-resource-mode

— same error • Deleting the cron deployment — fails earlier at the configmap patch •

--chart-version=1.7.2

— not viable, V1 chart is incompatible with Airbyte 2.1.0 Ask: • Is there a non-destructive way to resolve the configmap patch conflict on Helm chart V2 / Airbyte 2.1.0?