@kapa.ai is the storage path

/storage/airbyte-storage/

or

/storage/airbyte-bucket/

(or both?) for job-logging, workload output, etc? (Considering Airbyte Core 2.2.0 via helm install)

Thinking completed The provided knowledge sources do not explicitly mention the paths

/storage/airbyte-storage/

or

/storage/airbyte-bucket/

. In Airbyte Helm chart v2 deployments (including chart 2.2.0), document storage is organized by bucket/container names and internal object prefixes: 1. Bucket Name: Configured in your

values.yaml

under

global.storage.bucket

[Values]global storage: bucket: log: airbyte-bucket state: airbyte-bucket workloadOutput: airbyte-bucket auditLogging: airbyte-bucketThe name is user-defined (for example,

airbyte-bucket

or

airbyte

), not fixed by the platform [Values; helm chart v2 cannot connect to external minio]. 2. Internal Object Prefixes: Within the configured bucket or storage client, Airbyte uses the following hardcoded prefixes for each document type [Allow prefix override for buckets]: ◦ Job Logs:

job-logging

◦ Workload Output:

/workload/output

◦ State:

/state

◦ Activity Payloads:

/activity-payloads

◦ Audit Logs:

audit-logging

If you are looking at paths on local or bundled MinIO volumes, neither

/storage/airbyte-storage/

nor

/storage/airbyte-bucket/

is explicitly documented as a standard path in the provided sources. Objects are stored under the bucket name you configure, followed by the relevant document prefix (such as

job-logging/

or

workload/output/

) [Allow prefix override for buckets]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.