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
I am working with our engineering team to setup a self-hosted Hasura instance. They are wanting to connect to Big Query. To do this, we would like to use GKE Workload Identity Binding. This eliminates the need to use JSON keys in applications running on our GKE cluster.
Before we go through the hassle of installing all of this on our cluster, I am curious if this is possible, as the Hasura BigQuery docs require a Service Account Key EnvVar to be defined. Can we leave that blank, and will the connection work?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am working with our engineering team to setup a self-hosted Hasura instance. They are wanting to connect to Big Query. To do this, we would like to use GKE Workload Identity Binding. This eliminates the need to use JSON keys in applications running on our GKE cluster.
Before we go through the hassle of installing all of this on our cluster, I am curious if this is possible, as the Hasura BigQuery docs require a Service Account Key EnvVar to be defined. Can we leave that blank, and will the connection work?
Beta Was this translation helpful? Give feedback.
All reactions