Skip to content
Slipwaydocs

Google Cloud

Deploy to GKE and Cloud Run; read Cloud Monitoring; federate through Workload Identity Federation.

At a glance

Section titled “At a glance”
Category Cloud & Kubernetes
Authentication Workload Identity Federation (no service-account keys)
Provider id gcp

What it does

Section titled “What it does”
  • Cloud Run revisions and traffic splitting
  • GKE via Kubernetes integration
  • Cloud Monitoring metrics for verification

Set up

Section titled “Set up”
  1. Create the trust relationship on the cloud side (see the matching OIDC guide).
  2. In Settings, Integrations, add the connection and choose the runner pool that can reach it.
  3. Create an Infrastructure on an environment that references the connection.
  4. Use Test infrastructure to confirm connectivity before the first deployment.

Configuration

Section titled “Configuration”

Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.

provider: gcp
config:
  project_id: acme-prod
  workload_identity_provider: projects/123/locations/global/workloadIdentityPools/slipway/providers/slipway
  service_account: deployer@acme-prod.iam.gserviceaccount.com

Notes

Section titled “Notes”

See OIDC with GCP.

Section titled “Related”