Getting the Yandex Lockbox secret value on the Kubernetes side

Workload identity federations allow you to configure a link between external systems and Yandex Cloud via the OpenID Connect (OIDC) protocol. This allows external systems to perform actions on Yandex Cloud resources on behalf of service accounts without using authorized keys. This is a more secure method that minimizes the risk of credential leakage and the possibility of unauthorized access.

This tutorial shows you as an example how to get the Yandex Lockbox secret value from the Kubernetes side under a Yandex Cloud service account. Similarly, you can perform any action via the Yandex Cloud CLI, API, or Terraform.

To get the Yandex Lockbox secret value under a Kubernetes account:

1. Prepare the Kubernetes cluster.
2. Get your cloud ready.
3. Configure a scenario in Kubernetes.

If you no longer need the resources you created, delete them.

Prepare the Kubernetes clusterPrepare the Kubernetes cluster

1. Create a new Kubernetes cluster or use an existing one.

   Make sure your cluster meets the following requirements:

   • You are using Kubernetes 1.20 or higher.
     Earlier Kubernetes versions use a different ServiceAccount token format incompatible with the instructions provided here.
   • You have configured kube-apiserver to support projection of ServiceAccount tokens.

   Note

   This tutorial applies to both public and private Kubernetes clusters.

2. Create a manifest named service-account.yaml with the following contents:

   apiVersion: v1
   kind: ServiceAccount
   metadata:
     name: wlif
   

3. Apply the manifest:

   kubectl apply -f service-account.yaml
   

4. To check the ServiceAccount resource you created, run this command:

   kubectl describe serviceaccount wlif
   

   Result:

   Name:                wlif
   Namespace:           default
   

   You will need the Name and Namespace field values to further configure integration on the Yandex Cloud side.

5. Create a manifest named pod.yaml with the following contents:

   apiVersion: v1
   kind: Pod
   metadata:
     name: test-wlif
   spec:
     containers:
     - image: nginx
       name: nginx
       volumeMounts:
       - mountPath: /var/run/secrets/tokens
         name: sa-token
     serviceAccountName: wlif
     volumes:
     - name: sa-token
       projected:
         sources:
         - serviceAccountToken:
             path: sa-token
             expirationSeconds: 7200
             audience: ycaud
   

   In the audience field, specify the token recipient, e.g., ycaud.

6. Apply the manifest:

   kubectl apply -f pod.yaml
   

7. Make sure the pod you created has the RUNNING status:

   kubectl get pod test-wlif
   

   Result:

   NAME        READY   STATUS    RESTARTS   AGE
   test-wlif   1/1     Running   0          1m
   

8. Get URL Issuer for your Kubernetes cluster:

   kubectl get --raw /.well-known/openid-configuration | jq -r .issuer
   

9. Create a file with a public key set (JWKS):

   kubectl get --raw /openid/v1/jwks > cluster-jwks.json
   

Get your cloud readyGet your cloud ready

Sign up for Yandex Cloud and create a billing account:

1. Go to the management console and log in to Yandex Cloud or create an account if you do not have one yet.
2. On the Yandex Cloud Billing page, make sure you have a billing account linked and it has the ACTIVE or TRIAL_ACTIVE status. If you do not have a billing account, create one.

If you have an active billing account, you can go to the cloud page to create or select a folder for your infrastructure to operate in.

Learn more about clouds and folders.

Required paid resourcesRequired paid resources

The infrastructure support costs include:

1. Fee for storing the secret and requests to the secret (see Yandex Lockbox pricing).
2. Fee for data storage in a bucket and data operations (see Object Storage pricing).

Upload a file with a public key set to a public bucketUpload a file with a public key set to a public bucket

1. Create a public bucket:

   Management console

   1. In the management console, select the folder where you want to create a bucket.
   2. Select Object Storage.
   3. In the top panel, click Create bucket.
   4. On the bucket creation page:

      1. Enter a name for the bucket according to the naming requirements.

      2. In the Object read access field, select Public.

      3. Click Create bucket to complete the operation.

2. Upload the cluster-jwks.json file you created earlier into the bucket:

   Management console

   1. Go to the new bucket.
   2. In the left-hand panel, select Objects.
   3. Click Upload objects.
   4. In the top panel, click Upload.
   5. In the window that opens, select the cluster-jwks.json file and click Open.
   6. Click Upload.
   7. Refresh the page.

3. Get a link to the uploaded file:

   Management console

   1. Click the file name.
   2. Click Get link in the top-right corner.
   3. Copy the link.

Create a workload identity federationCreate a workload identity federation

Create a custom secretCreate a custom secret

Create a service account.Create a service account.

1. Create a service account:

   Management console

   1. In the management console, select the folder where you want to create a service account.
   2. From the list of services, select Identity and Access Management.
   3. Click Create service account.
   4. Enter a name for the service account, e.g., sa-lockbox.
   5. Click Create.

2. Assign the lockbox.payloadViewer role for the folder to the service account:

   Management console

   1. On the management console home page, select a folder.
   2. Navigate to the Access bindings tab.
   3. Find the sa-lockbox account in the list and click .
   4. Click Edit roles.
   5. Click Add role in the dialog that opens and select the lockbox.payloadViewer role.

Link the service account to the FederationLink the service account to the Federation

Configure a scenario in KubernetesConfigure a scenario in Kubernetes

1. Fill in the variables:

   SA_ID="<service_account_ID>"
   SECRET_ID="<secret_ID>"
   

   Where:

   • SA_ID: Service account ID.
   • SECRET_ID: Custom secret ID.

2. Get the Kubernetes service account token:

   SA_TOKEN=`kubectl exec -it test-wlif -- cat /var/run/secrets/tokens/sa-token`
   

3. Exchange the Kubernetes service account token for the IAM token of the Yandex Cloud service account:

   IAMTOKEN=$(curl -sH "Content-Type: application/x-www-form-urlencoded" -d "grant_type=urn:ietf:params:oauth:grant-type:token-exchange&requested_token_type=urn:ietf:params:oauth:token-type:access_token&audience=$SA_ID&subject_token=$SA_TOKEN&subject_token_type=urn:ietf:params:oauth:token-type:id_token" -X POST https://auth.yandex.cloud/oauth/token | jq -r '.access_token')
   

4. Request the secret via the API using the Yandex Cloud IAM token:

   SECRET_DATA=$(curl -sH "Authorization: Bearer ${IAMTOKEN}" https://payload.lockbox.api.cloud.yandex.net/lockbox/v1/secrets/$SECRET_ID/payload)
   echo ${SECRET_DATA}
   

   Result:

   { "entries": [ { "key": "secret", "textValue": "67cH2£?pO********" } ], "versionId": "e6q8isknpcp7********" }
   

Delete the resources you createdDelete the resources you created

Some resources are not free of charge. Delete the resources you no longer need to avoid paying for them:

• Yandex Lockbox secret
• Object Storage bucket
• Service account

See alsoSee also

• Getting the Lockbox secret value on the GitLab side
• Getting the Lockbox secret value on the GitHub side