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

Modified README to reflect requirements for using CloudDebugger

Browse source
This commit is contained in:
Hamid Asaadi 2018-10-23 18:13:17 -04:00 • committed by Hamidreza Asaadi
parent d69f1a4f25
commit 1e47ee393a
1 changed files with 12 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

22
README.md
View file

@ -93,24 +93,30 @@ Find **Protocol Buffers Descriptions** at the [`./pb` directory](./pb).
1. Install tools specified in the previous section (Docker, kubectl, skaffold) 1. Install tools specified in the previous section (Docker, kubectl, skaffold)
1. Create a Google Kubernetes Engine cluster and make sure `kubectl` is pointing 2. Create a Google Kubernetes Engine cluster and make sure `kubectl` is pointing
to the cluster. to the cluster.
gcloud services enable container.googleapis.com gcloud services enable container.googleapis.com
gcloud container clusters create demo --enable-autoupgrade \ gcloud container clusters create demo --enable-autoupgrade \
--enable-autoscaling --min-nodes=3 --max-nodes=10 --num-nodes=5 --enable-autoscaling --min-nodes=3 --max-nodes=10 --num-nodes=5 \
-- scopes https://www.googleapis.com/auth/cloud_debugger
kubectl get nodes kubectl get nodes
2. Enable Google Container Registry (GCR) on your GCP project and configure the 3. Enable Google Container Registry (GCR) on your GCP project and configure the
`docker` CLI to authenticate to GCR: `docker` CLI to authenticate to GCR:
gcloud services enable containerregistry.googleapis.com gcloud services enable containerregistry.googleapis.com
gcloud auth configure-docker -q gcloud auth configure-docker -q
3. Set your project ID on image names: 4. (OPTIONAL) Allow GCP to access source code via Github. This step is necessary
if you are using Stackdriver Debugger.
gcloud debug source gen-repo-info-file --output-directory=./src/
5. Set your project ID on image names:
- Edit `skaffold.yaml`, update the `imageName:` fields that look like - Edit `skaffold.yaml`, update the `imageName:` fields that look like
`gcr.io/[PROJECT_ID]` with your own GCP project ID. `gcr.io/[PROJECT_ID]` with your own GCP project ID.
@ -120,17 +126,13 @@ Find **Protocol Buffers Descriptions** at the [`./pb` directory](./pb).
`image:` fields with `gcr.io/[...]` and change them to your own GCP project `image:` fields with `gcr.io/[...]` and change them to your own GCP project
ID. ID.
5. Run `skaffold run` from the root of this repository. This command: 6. Run `skaffold run` from the root of this repository. This command:
- builds the container images - builds the container images
- pushes them to GCR - pushes them to GCR
- applies the `./kubernetes-manifests` deploying the application to - applies the `./kubernetes-manifests` deploying the application to
Kubernetes. Kubernetes.
**Troubleshooting:** If you get "No space left on device" error on Google Cloud Shell, 7. Find the IP address of your application, then visit the application on your
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` instead.
6. Find the IP address of your application, then visit the application on your
browser to confirm installation. browser to confirm installation.
kubectl get service frontend-external kubectl get service frontend-external