8dabe7ff94
This removes hardcoded GCP project name from images and requires an explicit repository flag to skaffold. Also updating the cloudbuild.yaml for staging with the gcr.io/k8s-skaffold/skaffold image. Fixes #17.
24 lines
No EOL
744 B
YAML
24 lines
No EOL
744 B
YAML
# Cloudbuild.yaml to deploy to staging
|
|
#
|
|
# PREREQUISITES:
|
|
# - Cloud Build service account must have role: "Kubernetes Engine Developer"
|
|
|
|
# USAGE:
|
|
# GCP zone and GKE target cluster must be specified as substitutions
|
|
# Example invocation:
|
|
# `gcloud builds submit --config=cloudbuild.yaml --substitutions=_ZONE=us-central1-b,_CLUSTER=demo-app-staging .`
|
|
|
|
steps:
|
|
- id: 'Deploy application to cluster'
|
|
name: 'gcr.io/k8s-skaffold/skaffold:v0.18.0'
|
|
entrypoint: 'bash'
|
|
args:
|
|
- '-c'
|
|
- >
|
|
gcloud container clusters get-credentials --zone=$_ZONE $_CLUSTER;
|
|
skaffold run -f=skaffold.yaml --default-repo=gcr.io/$PROJECT_ID;
|
|
|
|
# Add more power, and more time, for heavy Skaffold build
|
|
timeout: '3600s'
|
|
options:
|
|
machineType: 'N1_HIGHCPU_8' |