Configuring Rancher Backup to use GCP Cloud Storage as Remote Storage Location

This document (000021206) is provided subject to the disclaimer at the end of this document.

Situation

Use Google Cloud Storage as the S3 backend to store Rancher Backup Operator backups offsite.

Resolution

Create a new bucket in Google Cloud Storage
Create a GCP serviceaccount in IAM & Admin
Give the GCP serviceaccount permissions to read, write, and delete objects in the bucket. The serviceaccount will require the roles/storage.objectAdmin role to read, write, and delete objects in the bucket.

Navigate to your buckets in cloud storage and select your newly created bucket.
Go to the cloud storage’s settings menu and navigate to the interoperability tab
Scroll down to Service account HMAC and press + CREATE A KEY FOR A SERVICE ACCOUNT
Select the GCP serviceaccount you created earlier and press CREATE KEY
Save the Access Key and Secret.
Create the credentials secret using the following documentation: https://ranchermanager.docs.rancher.com/reference-guides/backup-restore-configuration/backup-configuration#example-credentialsecret

Install the Backup Operator with a default S3 storage location. The S3 storage location yaml looks like this:

  credentialSecretName: s3-creds
  credentialSecretNamespace: default
  bucketName: rancher-backups
  region: us
  endpoint: storage.googleapis.com

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.