Skip to content

Commit 55c94f9

Browse files
authored
improve(docs): clarify gcs crednetials configuration for helm chart (#43385)
1 parent 9d2c99a commit 55c94f9

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

docs/enterprise-setup/implementation-guide.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -356,20 +356,19 @@ Set `authenticationType` to `instanceProfile` if the compute infrastructure runn
356356
</TabItem>
357357
<TabItem value="GCS" label="GCS" default>
358358

359-
Ensure you've already created a Kubernetes secret containing the credentials blob for the service account to be assumed by the cluster. By default, secrets are expected in the `gcp-cred-secrets` Kubernetes secret, under a `gcp.json` file. Steps to configure these are in the above [prerequisites](#configure-kubernetes-secrets).
359+
Ensure you've already created a Kubernetes secret containing the credentials blob for the service account to be assumed by the cluster. Steps to configure these are in the above [prerequisites](#configure-kubernetes-secrets).
360360

361361
```yaml
362362
global:
363363
storage:
364364
type: "GCS"
365-
storageSecretName: gcp-cred-secrets
365+
storageSecretName: airbyte-config-secrets
366366
bucket: ## GCS bucket names that you've created. We recommend storing the following all in one bucket.
367367
log: airbyte-bucket
368368
state: airbyte-bucket
369369
workloadOutput: airbyte-bucket
370370
gcs:
371371
projectId: <project-id>
372-
credentialsPath: /secrets/gcs-log-creds/gcp.json
373372
```
374373

375374
</TabItem>

0 commit comments

Comments
 (0)