Explain cassandra deployment limitations (#26)

* Explain cassandra deployment limitations * Add comment why scaling down does not work
jaegertracing · Aug 7, 2017 · 9105f18 · 9105f18
1 parent 2fa3bdc
commit 9105f18
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/README.md b/README.md
@@ -32,7 +32,9 @@ Once everything is ready, `kubectl get service jaeger-query` tells you where to
 
 ### Persistent storage
 Even though this template uses a stateful Cassandra, backing storage is set to `emptyDir`. It's more
-appropriate to create a `PersistentVolumeClaim`/`PersistentVolume` and use it instead.
+appropriate to create a `PersistentVolumeClaim`/`PersistentVolume` and use it instead. Note that this
+Cassandra deployment does not support deleting pods or scaling down, as this might require 
+administrative tasks that are dependent on the final deployment architecture.
 
 ## Uninstalling