How to Configure Google Cloud Storage

1. Login in to Google Cloud Platform, navigate to google cloud storage and click create bucket.

1. Provide a name for your bucket and then click the “Continue” button

1. Go to Settings, open the “Interoperability” tab, and click Create Key for Another Service Account at the bottom.

• If using an existing service account, click “Create Key”.

• If creating a new service account:
  • Enter a service account name, optionally provide a description, and review the auto-generated Service Account ID and email. Once done, click Create and Continue to proceed.

1. An Access key and Service key will be generated. Store the Access key and Secret key in a safe place. This is your only chance to view and save the secret access key.

1. After creating an Access key and Secret key, use them to deploy the Blink Runner. Follow the instructions below for Kubernetes or Docker deployment:

​

Deploying the Runner in Kubernetes​

1. Run the Helm command provided by Blink, but make sure to include the additional configurations below to enable object storage for the runner:

    --set storage.s3.accessKeyId=<access_key_id> \    --set storage.s3.secretAccessKey=<secret_access_key>\    --set config.storage.execution.bucket=blink-runner-bucket \    --set config.storage.execution.region=us-east-1

• Replace <access_key_id> and <secret_access_key> with the credentials created in Step 4
• Replace blink-runner-bucket with the bucket name created in Step 2
• Ensure the region matches your bucket’s region

​

Deploying the Runner in Docker​

1. Run the Helm command provided by Blink, but make sure to include the additional configurations below to enable object storage for the runner:

-e STORAGE_S3_ACCESS_KEY_ID=YOUR_GCS_ACCESS_KEY \-e STORAGE_S3_SECRET_ACCESS_KEY=YOUR_GCS_SECRET_KEY \-e STORAGE_EXECUTION_BUCKET='{"region":"us-east-1","bucket":"your-bucket-name","endpoint":"https://storage.googleapis.com"}' \

• Replace <YOUR_GCS_ACCESS_KEY> and <YOUR_GCS_SECRET_KEY> with the credentials created in Step 4
• Replace <auth_key> with the authentication key for the runner.
• Ensure the region matches your bucket’s region
• Replace “your-bucket-name” with the bucket name created in Step 2