Hey everyone, I’m deploying Airbyte on EKS using Helm v2. I want to configure heartbeat and job timeouts (e.g., heartbeat-max-seconds-between-messages) via

values.yaml

. https://docs.airbyte.com/platform/understanding-airbyte/heartbeats Questions: 1. Is it possible to configure runtime flags (like heartbeat-max-seconds-between-messages) via

values.yaml

in Helm v2? 2. If yes, under which section should these flags go (

airbyte:

vs

airbyteBootloader:

)? 3. If no, what is the recommended way to set these values in EKS deployment? Thanks for clarification!

1. The provided Helm v2 and values.yaml docs only show mappings for environment variables and chart fields; they do not mention any way to configure heartbeat / destination timeout flags (such as

heartbeat-max-seconds-between-messages

,

heartbeat.failSync

,

destination-timeout-max-seconds

,

destination-timeout.failSync

) via

values.yaml

or Helm at all.[[Heartbeats tech](https://docs.airbyte.com/platform/understanding-airbyte/heartbeats#technical-details); [Helm v2 values mapping](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#update-your-valuesyaml-file)] Based on the knowledge sources, there is no documented support for setting these runtime flags through Helm v2 values. 2. Because there is no documented way to map those flags into

values.yaml

, the docs do not specify whether they would belong under

airbyte

,

airbyteBootloader

, or any other section. So this is not defined in the available documentation. 3. The only documented way to configure these heartbeat and destination timeout settings is via the

flags.yaml

file itself, not through Helm.[[Heartbeats tech](https://docs.airbyte.com/platform/understanding-airbyte/heartbeats#technical-details)] The docs describe: -

heartbeat-max-seconds-between-messages

-

heartbeat.failSync

-

destination-timeout-max-seconds

-

destination-timeout.failSync

all as entries in

flags.yaml

, with no mention of Kubernetes- / Helm-specific overrides.[[Heartbeats tech](https://docs.airbyte.com/platform/understanding-airbyte/heartbeats#technical-details)] So, from the available documentation: - You cannot (documentedly) configure these flags via Helm v2

values.yaml

. - They do not have a documented section in

values.yaml

. - The recommended/configured way in an EKS deployment remains editing and providing

flags.yaml

directly. The docs do not describe any additional EKS‑specific mechanism beyond that.