@kapa.ai When trying to initiate a sync, the source discover pod reports the following error: 2026-02-20 021612,965 [main] INFO i.m.r.Micronaut(start):183 - No embedded container found. Running as CLI application Exception in thread "main" io.micronaut.context.exceptions.BeanInstantiationException: Error instantiating bean of type [io.airbyte.workers.workload.WorkloadOutputWriter] Message: /secrets/gcs-log-creds/gcp.json Caused by: java.nio.file.NoSuchFileException: /secrets/gcs-log-creds/gcp.json

The error means the pod expects a GCS credentials file at

/secrets/gcs-log-creds/gcp.json

, but that file is not mounted into the container. From the docs and related issues, there are two key pieces to check: 1. Kubernetes Secret with

gcp.json

You must have a secret (commonly

airbyte-config-secrets

) that contains the GCP service account JSON under the key `gcp.json`:

yaml    apiVersion: v1    kind: Secret    metadata:      name: airbyte-config-secrets    type: Opaque    stringData:      gcp.json: <CREDENTIALS_JSON_BLOB>

Or via `kubectl`:

bash    kubectl create secret generic airbyte-config-secrets \      --from-file=gcp.json=./gcp.json \      --namespace airbyte

[[K8s secret](https://docs.airbyte.com/platform/enterprise-setup/implementation-guide#creating-a-kubernetes-secret)] 2. Helm values: storage + container orchestrator a. Storage configuration (GCS) In

values.yaml

, configure GCS storage to use that secret and path:

yaml    global:      storage:        type: "GCS"        secretName: airbyte-config-secrets        bucket:          log: airbyte-bucket          state: airbyte-bucket          workloadOutput: airbyte-bucket        gcs:          projectId: <project-id>          credentialsJsonPath: /secrets/gcs-log-creds/gcp.json

[[GCS storage](https://docs.airbyte.com/platform/deploying-airbyte/integrations/storage#values)] b. Mounting the secret for jobs / container orchestrator For some Helm versions, you must explicitly tell the container orchestrator which secret to mount and where, so that

/secrets/gcs-log-creds/gcp.json

exists in all job pods:

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, and ensure that secret contains

gcp.json

. [[GCP JSON mount](https://github.com/airbytehq/airbyte/issues/65153)] If after this the file is still missing, the knowledge sources do not provide further troubleshooting steps specific to your case; you would then need to inspect the running pod (

kubectl describe pod

/

kubectl exec

) to confirm the volume and file are present.