Skip to content

workload_identity.md

Latest commit

 

History

History
259 lines (186 loc) · 7.98 KB

workload_identity.md

File metadata and controls

259 lines (186 loc) · 7.98 KB

Distributed load testing with GKE & Workload Identity

NOTE The below instructions to for multi instance load operations deploy as a kubernetes deployment. This means that kubernetes will continuously restart your load or run instances until you manually stop them. It is important that you do not leave them running indefinitely.

Setup Environment

export PROJECT_ID=spanner-test
export SPANNER_INSTANCE=test-instance
export SPANNER_DATABASE=test-database
export GKE_CLUSTER_NAME=test-cluster
export GCP_REGION=us-west2
export GSA_NAME=gcsb-test-sa

Create a GCP Project

gcloud projects create $PROJECT_ID

Enable services

gcloud services enable spanner.googleapis.com --project $PROJECT_ID
gcloud services enable cloudbuild.googleapis.com --project $PROJECT_ID
gcloud services enable container.googleapis.com --project $PROJECT_ID
gcloud services enable artifactregistry.googleapis.com --project $PROJECT_ID

Create a service account

gcloud iam service-accounts create $GSA_NAME \
    --description="GCSB Test Account" \
    --display-name="gcsb" \
    --project $PROJECT_ID

Grant access to spanner

gcloud projects add-iam-policy-binding $PROJECT_ID \
    --member="serviceAccount:$GSA_NAME@${PROJECT_ID}.iam.gserviceaccount.com" \
    --role="roles/spanner.databaseUser"

Setup Spanner Database

Create a Spanner Instance

gcloud alpha spanner instances create $SPANNER_INSTANCE --config=regional-us-east1 --processing-units=1000 --project $PROJECT_ID

Create a database

gcloud spanner databases create $SPANNER_DATABASE --instance=$SPANNER_INSTANCE --project $PROJECT_ID

Setup GKE

Create GKE Cluster

Please see gcloud compute machine-types list for a list of machine types

gcloud container clusters create $GKE_CLUSTER_NAME \
  --project $PROJECT_ID \
  --region $GCP_REGION \
  --workload-pool=$PROJECT_ID.svc.id.goog \
  --machine-type=n1-standard-8 \
  --num-nodes 3

Create a namespace

kubectl create namespace gcsb

Create a kubernetes service account

kubectl create serviceaccount gcsb \
  --namespace gcsb

Allow kubernetes service account to impersonate google service account

gcloud iam service-accounts add-iam-policy-binding $GSA_NAME@$PROJECT_ID.iam.gserviceaccount.com \
    --role roles/iam.workloadIdentityUser \
    --member "serviceAccount:$PROJECT_ID.svc.id.goog[gcsb/gcsb]"

Add IAM annotation to kubernetes service account

kubectl annotate serviceaccount gcsb \
    --namespace gcsb \
    iam.gke.io/gcp-service-account=$GSA_NAME@$PROJECT_ID.iam.gserviceaccount.com

Build Docker Container

gcloud builds submit --tag gcr.io/$PROJECT_ID/gcsb .

Run the tool

Multi instance load operation

To create a load operation named 'gcsb-load', you must edit the wi_load.yaml file, supplying your spanner information.

For example, everywhere you se the comment EDIT: you must specify your information.

          - --project=YOUR_PROJECT_ID   # EDIT: Your GCP Project ID
          - --instance=YOUR_INSTANCE_ID # EDIT: Your Spanner Instance ID
          - --database=YOUR_DATABASE    # EDIT: Your Spanner Database Name
          - --table=YOUR_TABLE          # EDIT: Your Table Name
          - --operations=1000000        # EDIT: Number of Operations
          - --threads=10                # EDIT: Number of Threads

Once you have completed the necessary file edits, run the following.

kubectl apply -f docs/wi_load.yaml

to stop the test

kubectl delete deploy gcsb-load

Multi instance run operation

To create a load operation named 'gcsb-run', you must edit the wi_run.yaml file, supplying your spanner information.

For example, everywhere you se the comment EDIT: you must specify your information.

          - --project=YOUR_PROJECT_ID   # EDIT: Your GCP Project ID
          - --instance=YOUR_INSTANCE_ID # EDIT: Your Spanner Instance ID
          - --database=YOUR_DATABASE    # EDIT: Your Spanner Database Name
          - --table=YOUR_TABLE          # EDIT: Your Table Name
          - --operations=1000000        # EDIT: Number of Operations
          - --threads=10                # EDIT: Number of Threads
          - --reads=50                  # EDIT: Read Weight (Example: 50 = 50% reads)
          - --writes=50                 # EDIT: Write Weight (Example: 50 = 50% writes)
          - --sample-size=5             # EDIT: Percentage of table to sample for generating reads (Example: 5 = 5% of the rows in the table)

Once you have completed the necessary file edits, run the following.

kubectl apply -f docs/wi_run.yaml

to stop the test

kubectl delete deploy gcsb-run

Custom Configuration

If you prefer to mount your custom gcsb file into the container, you should follow these instructions

Create Configmap

The below example assumes your conig file is named gcsb.yaml

kubectl create configmap gcsb-config --from-file=gcsb.yaml --namespace=gcsb

Multi instance load operation

To create a load operation named 'gcsb-load', you must edit the wi_load_custom.yaml file, supplying your spanner information.

For example, everywhere you se the comment EDIT: you must specify your information.

          - --table=YOUR_TABLE              # EDIT: Your Table Name

Once you have completed the necessary file edits, run the following.

kubectl apply -f docs/wi_load_custom.yaml

to stop the test

kubectl delete deploy gcsb-load

Multi instance run operation

To create a load operation named 'gcsb-run', you must edit the wi_run_custom.yaml file, supplying your spanner information.

For example, everywhere you se the comment EDIT: you must specify your information.

          - --table=YOUR_TABLE              # EDIT: Your Table Name

Once you have completed the necessary file edits, run the following.

kubectl apply -f docs/wi_run_custom.yaml

to stop the test

kubectl delete deploy gcsb-run

Troubleshooting

Kubectl errors

SchemaError(io.k8s.api.autoscaling.v2beta2.MetricTarget): invalid object doesn't have additional properties

There are issues with some kubectl installations from homebrew. Please relink your kubectl installation by following these instructions.