@kapa.ai Can we add extra volumes/volumemounts to the dynamically created sync/check/etc pods via the helm chart?

Thinking completed The knowledge sources do not contain enough information to give a confident answer about adding extra volumes/volumeMounts to dynamically created sync/check/discover pods via the Helm chart. What the knowledge sources do confirm: • You can configure node selectors, annotations, tolerations, image pull policies/secrets, and namespace for job pods via environment variables or Helm chart V2 values. [Configuring Airbyte Jobs] [Helm Chart V2 Values] • Airbyte's Kubernetes pod process uses a shared volume internally (for config files, named pipes, etc.), but this is an internal implementation detail, not a user-configurable extra volume. [Forum: Shared Mount Volumes] • A forum question was raised about exactly this use case (adding volume mounts to worker pods so source/destination containers can access a NAS), but no definitive answer was provided in the knowledge sources. [Forum: Volume Mounts] Recommendation: There is no documented `extraVolumes`/`extraVolumeMounts` equivalent for the dynamically spun-up job pods (as opposed to the static worker/launcher pods themselves) in the knowledge sources available. For the most accurate answer, I'd suggest: 1. Checking the Airbyte Helm chart values reference directly on GitHub. 2. Asking in the Airbyte Slack community or Airbyte forum where the engineering team can confirm whether this is supported. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.