vbatts/microservices-demo
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Update instructions for Istio-installed GKE

Browse source 
Updated instructions to match Option 2 and provide more detail on command being run + add the troubleshooting section as users may run into the same issue with 'no space left on device'.
This commit is contained in:
cloud-pharaoh 2020-03-24 14:03:12 -07:00 • committed by GitHub
parent ccff406cdc
commit 087861346a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

16
README.md
View file

@ -249,7 +249,21 @@ by deploying the [release manifest](./release) directly to an existing cluster.
kubectl apply -f ./istio-manifests
```
5. Deploy the application with `skaffold run --default-repo=gcr.io/[PROJECT_ID]`.
5. In the root of this repository, run `skaffold run --default-repo=gcr.io/[PROJECT_ID]`,
where [PROJECT_ID] is your GCP project ID.
This command:
- builds the container images
- pushes them to GCR
- applies the `./kubernetes-manifests` deploying the application to
Kubernetes.
**Troubleshooting:** If you get "No space left on device" error on Google
Cloud Shell, you can build the images on Google Cloud Build: [Enable the
Cloud Build
API](https://console.cloud.google.com/flows/enableapi?apiid=cloudbuild.googleapis.com),
then run `skaffold run -p gcb --default-repo=gcr.io/[PROJECT_ID]` instead.
6. Run `kubectl get pods` to see pods are in a healthy and ready state.