GKE Workload Identity

This page provides information on configuring GKE Workload Identity for GKE in GCP.

Workload Identities (configured through Kubernetes service accounts to impersonate Google Service Accounts) can be used to assume a configure roles to provide access and permissions to GKE services. For example, if you have a Skill that calls for a connection, you can use a workload identity in lieu of providing an GCP API tokens (access key and secret key).

In GCP, resources are organized under “projects.” Customers can deploy all of their Google Cloud resources under a single project, or create separate projects to organize resources into logical groupings. Workload Identities can then be used to define access and authorization for each project.

For details about native Workload Identity support read this