Access secrets stored outside GKE clusters using client libraries

Prepare the environment

Clone the GitHub repository that contains the sample files for this tutorial:

gitclonehttps://github.com/GoogleCloudPlatform/kubernetes-engine-samples
cd~/kubernetes-engine-samples/security/wi-secrets

Create a secret in Secret Manager

1. The following example shows the data you'll use to create a secret:

   key=my-api-key

2. Create a secret to store the sample data:

   gcloudsecretscreatebq-readonly-key\
   --data-file=manifests/bq-readonly-key\
   --ttl=3600s
   

   This command does the following:

   • Creates a new Secret Manager secret with the sample key in the us-central1 Google Cloud region.
   • Sets the secret to expire one hour after you run the command.

Create the cluster and Kubernetes resources

Create a GKE cluster, Kubernetes namespaces, and Kubernetes service accounts. You create two namespaces, one for read-only access and one for read-write access to the secret. You also create a Kubernetes service account in each namespace to use with Workload Identity Federation for GKE.

1. Create a GKE Autopilot cluster:

   gcloudcontainerclusterscreate-autosecret-cluster\
   --location=us-central1
   

   The cluster might take about five minutes to deploy. Autopilot clusters always have Workload Identity Federation for GKE enabled. If you want to use a GKE Standard cluster instead, you must manually enable Workload Identity Federation for GKE before you continue.

2. Create a readonly-ns namespace and an admin-ns namespace:

   kubectlcreatenamespacereadonly-ns
   kubectlcreatenamespaceadmin-ns
   

3. Create a readonly-sa Kubernetes service account and an admin-sa Kubernetes service account:

   kubectlcreateserviceaccountreadonly-sa--namespace=readonly-ns
   kubectlcreateserviceaccountadmin-sa--namespace=admin-ns
   

Create IAM allow policies

1. Grant the readonly-sa service account read-only access to the secret:

   gcloudsecretsadd-iam-policy-bindingbq-readonly-key\
   --member=principal://iam.googleapis.com/projects/PROJECT_NUMBER/locations/global/workloadIdentityPools/PROJECT_ID.svc.id.goog/subject/ns/readonly-ns/sa/readonly-sa\
   --role='roles/secretmanager.secretAccessor'\
   --condition=None
   

   Replace the following:

   • PROJECT_NUMBER: your numerical Google Cloud project number.
   • PROJECT_ID: your Google Cloud project ID.

2. Grant the admin-sa service account read-write access to the secret:

   gcloudsecretsadd-iam-policy-bindingbq-readonly-key\
   --member=principal://iam.googleapis.com/projects/PROJECT_NUMBER/locations/global/workloadIdentityPools/PROJECT_ID.svc.id.goog/subject/ns/admin-ns/sa/admin-sa\
   --role='roles/secretmanager.secretAccessor'\
   --condition=None
   gcloudsecretsadd-iam-policy-bindingbq-readonly-key\
   --member=principal://iam.googleapis.com/projects/PROJECT_NUMBER/locations/global/workloadIdentityPools/PROJECT_ID.svc.id.goog/subject/ns/admin-ns/sa/admin-sa\
   --role='roles/secretmanager.secretVersionAdder'\
   --condition=None
   

Verify secret access

Deploy test Pods in each namespace to verify the read-only and read-write access.

1. Review the read-only Pod manifest:

   # Copyright 2022 Google LLC
   #
   # Licensed under the Apache License, Version 2.0 (the "License");
   # you may not use this file except in compliance with the License.
   # You may obtain a copy of the License at
   #
   # http://www.apache.org/licenses/LICENSE-2.0
   #
   # Unless required by applicable law or agreed to in writing, software
   # distributed under the License is distributed on an "AS IS" BASIS,
   # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   # See the License for the specific language governing permissions and
   # limitations under the License.
   apiVersion:v1
   kind:Pod
   metadata:
   name:readonly-test
   namespace:readonly-ns
   spec:
   containers:
   -image:google/cloud-sdk:slim
   name:workload-identity-test
   command:["sleep","infinity"]
   resources:
   requests:
   cpu:"150m"
   memory:"150Mi"
   serviceAccountName:readonly-sa

   This Pod uses the readonly-sa service account in the readonly-ns namespace.

2. Review the read-write Pod manifest:

   # Copyright 2022 Google LLC
   #
   # Licensed under the Apache License, Version 2.0 (the "License");
   # you may not use this file except in compliance with the License.
   # You may obtain a copy of the License at
   #
   # http://www.apache.org/licenses/LICENSE-2.0
   #
   # Unless required by applicable law or agreed to in writing, software
   # distributed under the License is distributed on an "AS IS" BASIS,
   # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   # See the License for the specific language governing permissions and
   # limitations under the License.
   apiVersion:v1
   kind:Pod
   metadata:
   name:admin-test
   namespace:admin-ns
   spec:
   containers:
   -image:google/cloud-sdk:slim
   name:workload-identity-test
   command:["sleep","infinity"]
   resources:
   requests:
   cpu:"150m"
   memory:"150Mi"
   serviceAccountName:admin-sa

   This Pod uses the admin-sa service account in the admin-ns namespace.

3. Deploy the test Pods:

   kubectlapply-fmanifests/admin-pod.yaml
   kubectlapply-fmanifests/readonly-pod.yaml
   

   The Pods might take a few minutes to start running. To monitor progress, run the following command:

   watchkubectlgetpods-nreadonly-ns
   

   When the Pod status changes to RUNNING, press Ctrl+C to return to the command-line.

Test read-only access

1. Open a shell in the readonly-test Pod:

   kubectlexec-itreadonly-test--namespace=readonly-ns--/bin/bash
   

2. Try to read the secret:

   gcloudsecretsversionsaccess1--secret=bq-readonly-key
   

   The output is key=my-api-key.

3. Try to write new data to the secret:

   printf"my-second-api-key"|gcloudsecretsversionsaddbq-readonly-key--data-file=-
   

   The output is similar to the following:

   ERROR: (gcloud.secrets.versions.add) PERMISSION_DENIED: Permission 'secretmanager.versions.add' denied for resource 'projects/PROJECT_ID/secrets/bq-readonly-key' (or it may not exist).
   

   The Pod using the read-only service account can only read the secret, and can't write new data.

4. Exit the Pod:

   exit
   

Test read-write access

1. Open a shell in the admin-test Pod:

   kubectlexec-itadmin-test--namespace=admin-ns--/bin/bash
   

2. Try to read the secret:

   gcloudsecretsversionsaccess1--secret=bq-readonly-key
   

   The output is key=my-api-key.

3. Try to write new data to the secret:

   printf"my-second-api-key"|gcloudsecretsversionsaddbq-readonly-key--data-file=-
   

   The output is similar to the following:

   Created version [2] of the secret [bq-readonly-key].
   

4. Read the new secret version:

   gcloudsecretsversionsaccess2--secret=bq-readonly-key
   

   The output is my-second-api-key.

5. Exit the Pod:

   exit
   

The Pods only get the level of access you granted to the Kubernetes service account used in the Pod manifest. Any Pods that use the admin-sa Kubernetes account in the admin-ns namespace can write new versions of the secret, but any Pods in the readonly-ns namespace that use the readonly-sa Kubernetes service account can only read the secret.

Access secrets from your code

In this section, you do the following:

1. Deploy a sample application that reads your secret in Secret Manager using client libraries.

2. Check that the application can access your secret.

You should access Secret Manager secrets from your application code whenever possible, using the Secret Manager API.

1. Review the sample application source code:

   // Copyright 2022 Google LLC
   //
   // Licensed under the Apache License, Version 2.0 (the "License");
   // you may not use this file except in compliance with the License.
   // You may obtain a copy of the License at
   //
   // http://www.apache.org/licenses/LICENSE-2.0
   //
   // Unless required by applicable law or agreed to in writing, software
   // distributed under the License is distributed on an "AS IS" BASIS,
   // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   // See the License for the specific language governing permissions and
   // limitations under the License.
   packagemain
   import(
   "context"
   "fmt"
   "log"
   "os"
   secretmanager"cloud.google.com/go/secretmanager/apiv1"
   secretmanagerpb"google.golang.org/genproto/googleapis/cloud/secretmanager/v1"
   )
   funcmain(){
   // Get environment variables from Pod spec.
   projectID:=os.Getenv("PROJECT_ID")
   secretId:=os.Getenv("SECRET_ID")
   secretVersion:=os.Getenv("SECRET_VERSION")
   // Create the Secret Manager client.
   ctx:=context.Background()
   client,err:=secretmanager.NewClient (ctx)
   iferr!=nil{
   log.Fatalf("failed to setup client: %v",err)
   }
   deferclient.Close ()
   // Create the request to access the secret.
   accessSecretReq:=&secretmanagerpb.AccessSecretVersionRequest {
   Name:fmt.Sprintf("projects/%s/secrets/%s/versions/%s",projectID,secretId,secretVersion),
   }
   secret,err:=client.AccessSecretVersion(ctx,accessSecretReq)
   iferr!=nil{
   log.Fatalf("failed to access secret: %v",err)
   }
   // Print the secret payload.
   //
   // WARNING: Do not print the secret in a production environment - this
   // snippet is showing how to access the secret material.
   log.Printf("Welcome to the key store, here's your key:\nKey: %s",secret.Payload.Data)
   }
   

   This application calls the Secret Manager API to try and read the secret.

2. Review the sample application Pod manifest:

   # Copyright 2022 Google LLC
   #
   # Licensed under the Apache License, Version 2.0 (the "License");
   # you may not use this file except in compliance with the License.
   # You may obtain a copy of the License at
   #
   # http://www.apache.org/licenses/LICENSE-2.0
   #
   # Unless required by applicable law or agreed to in writing, software
   # distributed under the License is distributed on an "AS IS" BASIS,
   # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   # See the License for the specific language governing permissions and
   # limitations under the License.
   apiVersion:v1
   kind:Pod
   metadata:
   name:readonly-secret-test
   namespace:readonly-ns
   spec:
   containers:
   -image:us-docker.pkg.dev/google-samples/containers/gke/wi-secret-store:latest
   name:secret-app
   env:
   -name:PROJECT_ID
   value:"YOUR_PROJECT_ID"
   -name:SECRET_ID
   value:"bq-readonly-key"
   -name:SECRET_VERSION
   value:"latest"
   resources:
   requests:
   cpu:"125m"
   memory:"64Mi"
   serviceAccountName:readonly-sa

   This manifest does the following:

   • Creates a Pod in the readonly-ns namespace that uses the readonly-sa service account.
   • Pulls a sample application from a Google image registry. This application calls the Secret Manager API using the Google Cloud client libraries. You can view the application code in /main.go in the repository.
   • Sets environment variables for the sample application to use.

3. Replace environment variables in the sample application:

   sed-i"s/YOUR_PROJECT_ID/PROJECT_ID/g""manifests/secret-app.yaml"
   

4. Deploy the sample app:

   kubectlapply-fmanifests/secret-app.yaml
   

   The Pod might take a few minutes to start working. If the Pod needs a new node in your cluster, you might notice CrashLoopBackOff type events while GKE provisions the node. The crashes stop when the node provisions successfully.

5. Verify the secret access:

   kubectllogsreadonly-secret-test-nreadonly-ns
   

   The output is my-second-api-key. If the output is blank, the Pod might not be running yet. Wait a few minutes and try again.

Alternative approaches

If you need to mount your sensitive data to your Pods, use the Secret Manager add-on for GKE. This add-on deploys and manages the Google Cloud Secret Manager provider for the Kubernetes Secret Store CSI driver in your GKE clusters. For instructions, see Use Secret Manager add-on with GKE.

Providing secrets as mounted volumes has the following risks:

1. Mounted volumes are susceptible to directory traversal attacks.
2. Environment variables can be compromised due to misconfigurations such as opening a debug endpoint.

Whenever possible, we recommend that you programmatically access secrets through the Secret Manager API. For instructions, use the sample application in this tutorial or refer to Secret Manager client libraries.