Workload Identity in GKE to fetch data from Google Cloud Storage.

How to use Workload Identity in GKE to fetch data from Google Cloud Storage.

In this video, I will show you how to use Workload Identity in GKE to fetch data from Google Cloud Storage. Workload Identity allows your Kubernetes workloads to impersonate Google service accounts, which gives them access to Google Cloud APIs.

To get started, you will need to create a Kubernetes service account and a Google service account. You will also need to grant the Google service account permission to access the Google Cloud Storage bucket that you want to fetch data from.

Once you have created the service accounts and granted permissions, you can use the gcloud command-line tool to bind the Kubernetes service account to the Google service account. You can then use the kubectl command-line tool to deploy the modified workload workload.

In the deployment, you will need to specify the Kubernetes service account that you want to use and the name of the Google Cloud Storage bucket that you want to fetch data from.

Once you have deployed your workload, you can access the data from Google Cloud Storage using the NGINX container.

I hope this video was helpful. Please let me know if you have any questions in the comments below.

WHO AM I:
Hey friends, welcome to my YouTube channel @outofdevops . If you're new my name is Anto, here I talk about software engineering and software engineers. Don't forget to comment like and subscribe 👍🏻.

YOUTUBE GEAR:

MY SOCIAL LINKs:

GET IN TOUCH:

PS: Some of the links in this description are affiliate links that I get a kickback from 😜

[liamray]

Thank you for the explanation!
I was a bit scared of your hand in the end haha :)

[alexanderpopov]

Thank you, Anto, that was useful to me! ❤

[prajeetkumbhare]

I have followed the same but I am unable to put to delete files from bucket

[ggdio]

Whats the advantage of using Workload Identity istead of traditional KMS and service accouts?

[QuangPham-bclc]

i have create firewall but still can't access. And if we use workload identity, which SA will GKE use (SA of nodepool or SA of workload identity) to pull container image from image registry like GAR or GCR?

[harkiratsingh]

Hey thanks for the video.. I am doing the same thing where i need to fetch images for GCP artifact registry, however i am getting issue -> failed to pull and unpack image failed to resolve reference failed to authorize: failed to fetch oauth token: unexpected status from GET request to ....403 Forbidden, what to do here