Enabling GKE Workload Identity

5 years ago dzone.com

Summary: This is a summary of an article originally published by the source. Read the full original article here →

In this blog, I will talk about the GKE Workload Identity feature and why to use this feature. An application running on GKE must authenticate to use Google Services such as Google Cloud Storage (GCS), Cloud SQL, BigQuery, etc.

GKE Workload identity allows us to attach the service account to the Kubernetes pod and remove the hassle to manage the service account credentials JSON file within the pod or cluster.

Add permissions to the Google Service Account required by an application.

Bind the Google Service Account (GSA) and Kubernetes Service Account (KSA), so that KSA can use the permissions granted to GSA.

DevOps Articles