airbyte on premisse. Where I save the values.yaml we don't have that on our airbyte 2.0 version

For an on-premises Airbyte 2.0 deployment on Kubernetes using Helm, the

values.yaml

file is something you create yourself — it doesn't come pre-existing in your cluster. Here's how it works: Creating your values.yaml You create a new

values.yaml

file locally on the machine where you run Helm commands (e.g., your workstation or a bastion host). You only need to include the specific overrides for your configuration — you don't need to copy the entire chart's default values. [Installation Guide] A minimal example for Airbyte 2.0 (Community edition):

global:
  edition: community
  airbyteUrl: "" # The URL where Airbyte will be reached; This should match your Ingress host

Or for Enterprise:

global:
  edition: enterprise

  enterprise:
    secretName: "" # Secret name where an Airbyte license key is stored
    licenseKeySecretKey: "" # The key within `licenseKeySecretName` where the Airbyte license key is stored

  airbyteUrl: "" # The URL where Airbyte will be reached

[Upgrade to Helm chart V2 (Core); Enterprise Setup] Using it during installation Once you have your

values.yaml

file, you pass it to the Helm install command:

helm install airbyte airbyte-v2/airbyte \
  --namespace airbyte-v2 \
  --values ./values.yaml \
  --version 2.0.18

[Installation Guide] Key point The

values.yaml

is not stored inside Airbyte itself — it's a local configuration file you maintain and use when running Helm commands to install or upgrade your deployment. You can store it anywhere accessible from your Helm client (e.g., a Git repository, a local directory, etc.). For a full reference of all available configuration options, see the Values.yaml reference. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai where usually is the "*locally on the machine where you run Helm commands* (e.g., your workstation or a bastion host)" ?

The knowledge sources do not explicitly specify a recommended physical location or path for storing the

values.yaml

file on your local machine or bastion host. The documentation only states that it should be somewhere accessible during the installation process when running Helm commands. [Installation Guide] For example, the Helm install command references it as

./values.yaml

, implying it's in the current working directory from which you run the command:

helm install airbyte airbyte-v2/airbyte \
  --namespace airbyte-v2 \
  --values ./values.yaml \
  --version 2.0.18

[Installation Guide] The Enterprise documentation also mentions creating it inside an

airbyte

directory: > "you need to create an additional

values.yaml

file in your

airbyte

directory" [Enterprise Setup] Beyond that, the specific location is up to you — common practices (not stated in the docs) would be a Git repository or a dedicated config directory, but the docs don't prescribe a specific path. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai we are on linux

The knowledge sources do not contain specific information about Linux file system paths or conventions for storing the

values.yaml

file. The documentation only states it should be accessible when running Helm commands, and references it as

./values.yaml

(the current working directory). [Installation Guide] For anything beyond that — such as recommended Linux directory conventions — I'm not able to provide guidance based on the Airbyte documentation alone. A common general practice would be to keep it in a dedicated directory like

~/airbyte/values.yaml

, which aligns with the docs mentioning an

airbyte

directory [Enterprise Setup], but the docs don't prescribe a specific Linux path. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.