From ef9bc391722288d76c3820c7c6fa42f6833a2d77 Mon Sep 17 00:00:00 2001 From: Anthony Yeh Date: Tue, 29 Nov 2016 10:40:15 -0800 Subject: [PATCH] Address review comments --- .../run-replicated-stateful-application.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/tutorials/replicated-stateful-application/run-replicated-stateful-application.md b/docs/tutorials/replicated-stateful-application/run-replicated-stateful-application.md index 8299c08e57..299240f80c 100644 --- a/docs/tutorials/replicated-stateful-application/run-replicated-stateful-application.md +++ b/docs/tutorials/replicated-stateful-application/run-replicated-stateful-application.md @@ -171,6 +171,10 @@ The script in the `init-mysql` container also applies either `master.cnf` or Because the example topology consists of a single master and any number of slaves, the script simply assigns ordinal `0` to be the master, and everyone else to be slaves. +Combined with the StatefulSet controller's +[deployment order guarantee](/docs/concepts/controllers/statefulsets/#deployment-and-scaling-guarantee), +this ensures the master is Ready before creating slaves, so they can begin +replicating. #### Cloning existing data @@ -512,6 +516,11 @@ kubectl delete pvc data-mysql-4 kubectl delete configmap,service,pvc -l app=mysql ``` +* If you manually provisioned PersistentVolumes, you will also need to manually + delete them. If you used a dynamic provisioner, it will automatically delete + the PersistentVolumes when it sees you have deleted the + PersistentVolumeClaims above. + {% endcapture %} {% capture whatsnext %}