Skip to content

Commit dd14d1a

Browse files
author
mgoddard
committed
Revising README to match current state of demo
1 parent b75667f commit dd14d1a

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

README.md

+5-3
Original file line numberDiff line numberDiff line change
@@ -214,20 +214,22 @@ $ export USE_GEOHASH=true
214214
- Terminating one of the pods and verifying that the app remains available
215215
* The files in the `./k8s` subdirectory are used for a K8s deployment. They are:
216216

217-
- [`deploy_k8s.sh`](./k8s/deploy_k8s.sh): script to deploy a 4 VM K8s cluster in GKE
217+
- [`deploy_k8s.sh`](./k8s/deploy_k8s.sh): script to deploy a 5 VM K8s cluster in GKE
218218
- [`data-loader.yaml`](./k8s/data-loader.yaml): pod definition which loads the data
219219
- [`crdb-geo-tourist.yaml`](./k8s/crdb-geo-tourist.yaml): app deployment and load balancer service
220220
- [`cockroachdb.yaml`](./k8s/cockroachdb.yaml): an edited version of the `example.yaml` file provided in the operator docs (above)
221221
- [`create_user.sql`](./k8s/create_user.sql): used by the deployment script to create a role with a password
222+
- [`rolling_upgrade.yaml`](./k8s/rolling_upgrade.yaml): used to perform a zero-downtime rolling upgrade of CockroachDB
223+
- [`scale_out.yaml`](./k8s/scale_out.yaml): used to scale the 3 node cluster out to 4 nodes (also an online operation)
222224

223225
* Change to the `./k8s` directory: `cd ./k8s/`
224-
* Edit `./deploy_k8s.sh`, changing any of the following:
226+
* Edit `./deploy_k8s.sh`, changing any of the following to suit your needs:
225227

226228
```
227229
MACHINETYPE="e2-standard-4"
228230
NAME="${USER}-geo-tourist"
229231
ZONE="us-east4-b"
230-
N_NODES=4
232+
N_NODES=5
231233
```
232234
* Run the script and follow the prompts: `./deploy_k8s.sh`
233235

0 commit comments

Comments
 (0)