Aviad Deri
12/11/2025, 2:21 PMkapa.ai
12/11/2025, 2:22 PM/secrets/gcs-log-creds/gcp.json inside the MSSQL source pod: > Caused by: java.nio.file.NoSuchFileException: /secrets/gcs-log-creds/gcp.json From the issues and docs, this happens when: 1. The GCS credentials secret is not mounted into job/connector pods, or 2. The Helm values for the container orchestrator secret name/mount path don’t match where the file actually is, or 3. The GCS storage configuration keys differ between Helm v1 and v2. Relevant points from the knowledge sources: - Jobs/connector pods expect the GCP JSON at /secrets/gcs-log-creds/gcp.json and will fail if it’s missing. [[GCP JSON not mounted](https://github.com/airbytehq/airbyte/issues/65153); [Using container orchestrator](https://discuss.airbyte.io/t/2207)] - For Helm v2, you must explicitly configure the container orchestrator secret and mount path so that the GCP JSON is available in job pods: [[GCP JSON not mounted](https://github.com/airbytehq/airbyte/issues/65153)] yaml global: workloads: containerOrchestrator: secretName: "airbyte-gcs-logs-creds" secretMountPath: "/secrets/gcs-log-creds" (Replace "airbyte" in the secret name with your Helm release name.) [[GCP JSON not mounted](https://github.com/airbytehq/airbyte/issues/65153)] - When using GCS storage with Helm v2, some keys changed compared to v1 (case-sensitive type, and credentialsJsonSecretKey instead of credentialsPath). [[Container launcher not using creds](https://github.com/airbytehq/airbyte/issues/68177); [global.storage.secretName issue](https://github.com/airbytehq/airbyte/issues/48842)] So the issue is: the GCS credentials file is not present at /secrets/gcs-log-creds/gcp.json in the MSSQL source pod because the secret is not mounted (or not mounted at that path) for workload/connector pods. To fix, based on the sources: 1. Ensure you have a Kubernetes secret containing gcp.json (e.g. airbyte-gcs-logs-creds or <release-name>-gcs-logs-creds) with the key gcp.json. [[State & logging storage](https://docs.airbyte.com/platform/deploying-airbyte/integrations/storage#values)] 2. In your Helm values, set: yaml global: workloads: containerOrchestrator: secretName: "<your-release-name>-gcs-logs-creds" secretMountPath: "/secrets/gcs-log-creds" so that /secrets/gcs-log-creds/gcp.json exists in job/connector pods. [[GCP JSON not mounted](https://github.com/airbytehq/airbyte/issues/65153)] 3. If you’re on Helm v2 and using GCS for storage, also verify the global.storage section uses the correct keys (type: "GCS" or "gcs" depending on chart, and credentialsJsonSecretKey if applicable) as described in the issues. [[Container launcher not using creds](https://github.com/airbytehq/airbyte/issues/68177); [global.storage.secretName issue](https://github.com/airbytehq/airbyte/issues/48842)] Once the secret is correctly mounted at /secrets/gcs-log-creds with a gcp.json file, the WorkloadOutputWriter / GcsStorageClient should initialize and the MSSQL source pod should start successfully.