From 90e5971a525afabff900d2974f14964d81bdbda0 Mon Sep 17 00:00:00 2001 From: Janet Kuo Date: Mon, 21 Nov 2016 11:10:04 -0800 Subject: [PATCH] Remove alpha limitation on PetSet in cassandra example --- examples/storage/cassandra/README.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/examples/storage/cassandra/README.md b/examples/storage/cassandra/README.md index 06cdb500e04..5055fd816ea 100644 --- a/examples/storage/cassandra/README.md +++ b/examples/storage/cassandra/README.md @@ -396,16 +396,13 @@ functionality, like a Deployment, ReplicaSet, Replication Controller, or Job. ## Step 4: Delete Cassandra StatefulSet -There are some limitations with the Alpha release of PetSet in 1.3. From the [documentation](http://kubernetes.io/docs/user-guide/petset/): - -"Deleting the StatefulSet will not delete any pods. You will either have to manually scale it down to 0 pods first, or delete the pods yourself. -Deleting and/or scaling a StatefulSet down will not delete the volumes associated with the StatefulSet. This is done to ensure safety first, your data is more valuable than an auto purge of all related StatefulSet resources. Deleting the Persistent Volume Claims will result in a deletion of the associated volumes." +Deleting and/or scaling a StatefulSet down will not delete the volumes associated with the StatefulSet. This is done to ensure safety first, your data is more valuable than an auto purge of all related StatefulSet resources. Deleting the Persistent Volume Claims may result in a deletion of the associated volumes, depending on the storage class and reclaim policy. You should never assume ability to access a volume after claim deletion. Use the following commands to delete the StatefulSet. ```console $ grace=$(kubectl get po cassandra-0 --template '{{.spec.terminationGracePeriodSeconds}}') \ - && kubectl delete statefulset,po -l app=cassandra \ + && kubectl delete statefulset -l app=cassandra \ && echo "Sleeping $grace" \ && sleep $grace \ && kubectl delete pvc -l app=cassandra