From a7a3bb7e03042cca22f5b8694b505c7f39caf7ee Mon Sep 17 00:00:00 2001 From: Olivier Cervello Date: Thu, 16 Aug 2018 15:26:34 -0500 Subject: [PATCH 1/3] Update skaffold.yaml `skaffold run` will fail while building the `cartservice` with a 'No Space Left on Device Error' Increasing the disk allocated for the build (default 200GB) to get rid of this error. --- skaffold.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/skaffold.yaml b/skaffold.yaml index a05d6eb..a8a88b1 100644 --- a/skaffold.yaml +++ b/skaffold.yaml @@ -17,6 +17,8 @@ kind: Config build: tagPolicy: gitCommit: {} + googleCloudBuild: + diskSizeGb: 300 artifacts: - imageName: gcr.io/microservices-demo-app/emailservice workspace: src/emailservice From 0d6e54f8120f895c6a35b7fb518d60c7ce3bf29b Mon Sep 17 00:00:00 2001 From: Olivier Cervello Date: Mon, 20 Aug 2018 12:17:54 -0500 Subject: [PATCH 2/3] Increaes GCB VM disk space to avoid build failure Default VM disk size is 200 for Cloud Build, we need at least 300 to build all services. --- skaffold.yaml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/skaffold.yaml b/skaffold.yaml index a8a88b1..5389ac8 100644 --- a/skaffold.yaml +++ b/skaffold.yaml @@ -17,8 +17,6 @@ kind: Config build: tagPolicy: gitCommit: {} - googleCloudBuild: - diskSizeGb: 300 artifacts: - imageName: gcr.io/microservices-demo-app/emailservice workspace: src/emailservice @@ -44,3 +42,9 @@ deploy: kubectl: manifests: - ./kubernetes-manifests/**.yaml +profiles: + - name: gcb + build: + googleCloudBuild: + diskSizeGb: 300 + machineType: "N1_HIGHCPU_32" From 074048ef5a3f4ec72b3bf5fdb844773486771ad6 Mon Sep 17 00:00:00 2001 From: Ahmet Alp Balkan Date: Tue, 21 Aug 2018 10:27:35 -0700 Subject: [PATCH 3/3] skaffold.yaml: annotate gcb profile --- skaffold.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/skaffold.yaml b/skaffold.yaml index 5389ac8..86062e5 100644 --- a/skaffold.yaml +++ b/skaffold.yaml @@ -42,6 +42,15 @@ deploy: kubectl: manifests: - ./kubernetes-manifests/**.yaml + +# "gcb" profile allows building and pushing the images +# on Google Container Builder without requiring docker +# installed on the developer machine. However, note that +# since GCB does not cache the builds, each build will +# start from scratch and therefore take a long time. +# +# This is not used by default. To use it, run: +# skaffold run -p gcb profiles: - name: gcb build: