You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/integrate/redis-data-integration/data-pipelines/prepare-dbs/spanner.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ for more details, including additional configuration options and dialect-specifi
61
61
## 3. Create a service account
62
62
63
63
To allow RDI to access the Spanner instance, you'll need to create a service account with the
64
-
appropriate permissions. By default, RDI uses Google Cloud Workload Identity authentication
64
+
appropriate permissions. By default, RDI uses Google Cloud Workload Identity authentication. In this case RDI will assume the [service account is assigned to the GKE cluster](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#enable_on_clusters_and_node_pools)
65
65
when the service account is assigned to the GKE cluster. Alternatively, you can provide the
66
66
service account credentials as a Kubernetes secret (see step 4 for details).
67
67
@@ -127,7 +127,7 @@ Before deploying the RDI pipeline, you need to configure the necessary secrets f
127
127
database. Instructions for setting up the target database secrets are available in the
0 commit comments