{{announcement.body}}
{{announcement.title}}

Enabling GKE Workload Identity

DZone 's Guide to

Enabling GKE Workload Identity

In this article, I discuss GKE Workload Identity feature to achieve better security

· Cloud Zone ·
Free Resource

In this blog, I will talk about the GKE Workload Identity feature and why to use this feature.

What’s the Problem?

An application running on GKE must authenticate to use Google Services such as Google Cloud Storage (GCS), Cloud SQL, BigQuery, etc. Authentication can be done by providing a service account key JSON file to an application using Kubernetes Secret space or a different method such as Vault. 

But in these approaches, service account key JSON (which has 10years of a lifetime) must be stored in plain text within the pod or base64 encoded in Kubernetes secret space. Also, the key rotation process must be in a place that is not a fun process.

We can avoid using the service account key by attaching a service account to Kubernetes Node but then all the pods running on the Node gets the same permission which is not an ideal thing to do.

Goal?

We want to assign a service account to a Pod so we can isolate permissions for different pods.

Hurray, we have Workload Identity feature available in beta which solves this problem on GKE.

So, What is Workload Identity?

As per Google documentation, “Workload Identity is the recommended way to access Google Cloud services from within GKE due to its improved security properties and manageability.

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.

Workload Identity in a GKE Cluster

Prerequisites

  1. If you have not setup gcloud on your workstation, then refer my previous blog to get it up and running quickly.
    Alternatively, you can use Google Cloud Shell to run the commands.

  2. Make sure you are a Project Editor or Project Owner or have enough permissions to run the below commands.

Set Up a GKE Cluster

Follow the below step to create a new GKE Cluster and enable Workload Identity.

  1. Enable the Cloud IAM API.

  2. Set GCP defaults.

    • Set GCP Project

      Shell

    • Set default region and zone

      Shell

  3. Make sure you have kubectl command installed.

    Shell


    Run following to verify

    kubectl help
  4. Update gcloud commands.

    gcloud components update
  5. Create a new Google Service Account (GSA).

    Shell


    Notes: You can use the existing service account.
    Permission Required: iam.serviceAccounts.create on the GCP Project.

  6. Add permissions to the Google Service Account required by an application. For example, roles/storage.objectViewer

    Shell
  7. Setup a GKE cluster with Workload Identity enabled.

    Shell

    Notes: GKE Cluster could take 5-10mins to become fully functional.
    Permission required: container.clusters.create on the GCP Project.

  8. Configure kubectl command on your terminal.

    Shell


    Notes: This will populate ~/.kube/config file.
    Permission Required: container.clusters.get on the GCP Project.

  9. (Optional) Create a Kubernetes namespace if you dont want to use default namespace.

    kubectl create namespace newspace
  10. Create Kubernetes Service Account (KSA).

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

    Shell
  12. Add annotation

    Shell
  13. Create a Pod with the KSA created to verify.

    Shell


    Running above command will login to Pod and provides its bash shell. Now run below command to see which service account this pod is configured with.

    Shell

This should print the GSA name.

                           Credentialed Accounts
    ACTIVE  ACCOUNT
    *       workload-identity-test@workshop-demo-namwcb.iam.gserviceaccount.com

Cleanup

Don’t forget to cleanup the resources, once you no longer need it.
Run the following commands:

  1. Delete the GKE cluster.

    gcloud container clusters delete $GKE_CLUSTER_NAME
  2. Delete the Google Service Account (GSA).

    Shell

    Below is the terminal recording: Terminal recording of deployment

Hope this blog helps you get familiar with Workload Identity and securely deploy apps on GKE.

If you have feedback or questions, please reach out to me on LinkedIn or Twitter.

Topics:
access management, devops, gcp, gcp cloud, gke, kubernetes, security

Published at DZone with permission of Pradeep Bhadani . See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}