README.md: bump Tilt and Minikube

The Tilt release fixed the bug that used to require --update-mode
and has a number of nice usability improvements.

Minikube brings in a more recent k8s version.

Change-Id: I3a549328e4993ae284443224124a590311c3e5d2
This commit is contained in:
Leo 2021-06-22 20:21:13 +02:00 committed by Leopold Schabel
parent 22373b9943
commit de31d0d381
1 changed files with 4 additions and 4 deletions

View File

@ -6,10 +6,10 @@ The following dependencies are required for local development:
- [Go](https://golang.org/dl/) >= 1.15.6 - [Go](https://golang.org/dl/) >= 1.15.6
- [Docker](https://docs.docker.com/engine/install/) / moby-engine >= 19.03 - [Docker](https://docs.docker.com/engine/install/) / moby-engine >= 19.03
- [Tilt](http://tilt.dev/) >= 0.17.10 - [Tilt](http://tilt.dev/) >= 0.20.8
- [NodeJS/npm](https://nodejs.org/en/download/) >= 14 - [NodeJS/npm](https://nodejs.org/en/download/) >= 14
- Any of the local Kubernetes clusters supported by Tilt. - Any of the local Kubernetes clusters supported by Tilt.
We recommend [minikube](https://kubernetes.io/docs/setup/learning-environment/minikube/) with the kvm2 driver. We recommend [minikube](https://kubernetes.io/docs/setup/learning-environment/minikube/) >= v1.21.0 with the kvm2 driver.
See the [Tilt docs](https://docs.tilt.dev/install.html) docs on how to set up your local cluster - See the [Tilt docs](https://docs.tilt.dev/install.html) docs on how to set up your local cluster -
it won't take more than a few minutes to set up! Example minikube invocation, adjust limits as needed: it won't take more than a few minutes to set up! Example minikube invocation, adjust limits as needed:
@ -29,12 +29,12 @@ to avoid having to specify `-n wormhole` for all commands:
kubectl config set-context --current --namespace=wormhole kubectl config set-context --current --namespace=wormhole
After installing all dependencies, just run `tilt up --update-mode=exec`. After installing all dependencies, just run `tilt up`.
Whenever you modify a file, the devnet is automatically rebuilt and a rolling update is done. Whenever you modify a file, the devnet is automatically rebuilt and a rolling update is done.
Launch the devnet while specifying the number of guardians nodes to run (default is five): Launch the devnet while specifying the number of guardians nodes to run (default is five):
tilt up --update-mode=exec -- --num=1 tilt up -- --num=1
If you want to work on non-consensus parts of the code, running with a single guardian is easiest since If you want to work on non-consensus parts of the code, running with a single guardian is easiest since
you won't have to wait for k8s to restart all pods. you won't have to wait for k8s to restart all pods.