Skip to content
This repository has been archived by the owner on May 18, 2020. It is now read-only.

Explain cassandra deployment limitations #26

Merged
merged 2 commits into from
Aug 7, 2017
Merged

Explain cassandra deployment limitations #26

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
64773da
Explain cassandra deployment limitations
pavolloffay Aug 3, 2017
5aa48cf
Add comment why scaling down does not work
pavolloffay Aug 7, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down