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

Docker for Desktop instructions removed

Browse source 
Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
This commit is contained in:
Ihor Dvoretskyi 2018-08-31 19:21:38 +00:00
parent a5a1014027
commit 8112914a4a
1 changed files with 5 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
README.md
View file

@ -41,8 +41,7 @@ Find **Protocol Buffers Descriptions** at the [`./pb` directory](./pb).
## Features ## Features
- **[Kubernetes](https://kubernetes.io)/[GKE](https://cloud.google.com/kubernetes-engine/):** - **[Kubernetes](https://kubernetes.io)/[GKE](https://cloud.google.com/kubernetes-engine/):**
The app is designed to run on Kubernetes (both locally on Minikube and "Docker for The app is designed to run on Kubernetes (locally on Minikube, as well as on the cloud with GKE).
Desktop", as well as on the cloud with GKE).
- **[gRPC](https://grpc.io):** Microservices use a high volume of gRPC calls to - **[gRPC](https://grpc.io):** Microservices use a high volume of gRPC calls to
communicate to each other. communicate to each other.
- **[Istio](https://istio.io):** Application works on Istio service mesh. - **[Istio](https://istio.io):** Application works on Istio service mesh.
@ -64,23 +63,17 @@ Find **Protocol Buffers Descriptions** at the [`./pb` directory](./pb).
> **Note:** that the first build can take up to 20-30 minutes. Consequent builds > **Note:** that the first build can take up to 20-30 minutes. Consequent builds
> will be faster. > will be faster.
### Option 1: Running locally with “Docker for Desktop” ### Option 1: Running locally with Minikube
> 💡 Recommended if you're planning to develop the application. > 💡 Recommended if you're planning to develop the application.
1. Install tools to run a Kubernetes cluster locally: 1. Install tools to run a Kubernetes cluster locally:
- kubectl (can be installed via `gcloud components install kubectl`) - kubectl (can be installed via `gcloud components install kubectl`)
- One of the tools that deploy Kubernetes cluster locally: - Minikube (Linux/Mac/Windows). It's the open source, cross-platrorm tool, developed by the Kubernetes community. Installation instructions and documentation can be found [here](https://github.com/kubernetes/minikube).
- Minikube (Linux/Mac/Wimdows). It's the open source, cross-platrorm tool, developed by the Kubernetes community. Installation instructions and documentation can be found [here](https://github.com/kubernetes/minikube).
- Docker for Desktop (Mac/Windows): It provides Kubernetes support as [noted
here](https://docs.docker.com/docker-for-mac/kubernetes/).
- [skaffold](https://github.com/GoogleContainerTools/skaffold/#installation) - [skaffold](https://github.com/GoogleContainerTools/skaffold/#installation)
1. Launch the local Kubernetes cluster: 1. Launch the local Kubernetes cluster with `minikube start` command. More details can be found [here](https://github.com/kubernetes/minikube#quickstart).
- Launch Minikube with `minikube start` command. More details can be found [here](https://github.com/kubernetes/minikube#quickstart).
- Launch “Docker for Desktop”. Go to Preferences and choose “Enable Kubernetes”.
1. Run `kubectl get nodes` to verify that the local cluster works properly. 1. Run `kubectl get nodes` to verify that the local cluster works properly.
1. Run `skaffold run` (first time will be slow, it can take ~20-30 minutes). 1. Run `skaffold run` (first time will be slow, it can take ~20-30 minutes).
@ -95,7 +88,7 @@ Find **Protocol Buffers Descriptions** at the [`./pb` directory](./pb).
> 💡 Recommended for demos and making it available publicly. > 💡 Recommended for demos and making it available publicly.
1. Install tools specified in the previous section (Docker, kubectl, skaffold) 1. Install tools specified in the previous section (kubectl, skaffold)
1. Create a Google Kubernetes Engine cluster and make sure `kubectl` is pointing 1. Create a Google Kubernetes Engine cluster and make sure `kubectl` is pointing
to the cluster. to the cluster.