From 95f641f6da90c01d0c57016eaf9620dea45ce94d Mon Sep 17 00:00:00 2001
From: Jesse Dubay <jesse@thefortytwo.net>
Date: Wed, 24 May 2017 12:26:37 -0700
Subject: [PATCH] [stable/percona] Fix README to match default persistence
 settings (#1133)

The README for the Percona chart claims that persistence is enabled by
default, but `persistence.enabled` defaults to `false` in `values.yaml`.

Fixes #1128.
---
 stable/percona/README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/stable/percona/README.md b/stable/percona/README.md
index 59099e38cb..90c5c5a441 100644
--- a/stable/percona/README.md
+++ b/stable/percona/README.md
@@ -54,7 +54,7 @@ The following tables lists the configurable parameters of the Percona chart and
 | `perconaUser`                | Username of new user to create.    | `nil`                                                      |
 | `perconaPassword`            | Password for the new user.         | `nil`                                                      |
 | `perconaDatabase`            | Name for new database to create.   | `nil`                                                      |
-| `persistence.enabled`      | Create a volume to store data      | true                                                       |
+| `persistence.enabled`      | Create a volume to store data      | false                                                       |
 | `persistence.size`         | Size of persistent volume claim    | 8Gi RW                                                     |
 | `persistence.storageClass` | Type of persistent volume claim    | nil  (uses alpha storage class annotation)                 |
 | `persistence.accessMode`   | ReadWriteOnce or ReadOnly          | ReadWriteOnce                                              |
@@ -84,7 +84,8 @@ $ helm install --name my-release -f values.yaml stable/percona
 
 The [Percona Server](https://hub.docker.com/_/percona/) image stores the MySQL data and configurations at the `/var/lib/mysql` path of the container.
 
-By default a PersistentVolumeClaim is created and mounted into that directory. In order to disable this functionality
-you can change the values.yaml to disable persistence and use an emptyDir instead.
+By default, an emptyDir volume is mounted at that location.
 
 > *"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."*
+
+You can change the values.yaml to enable persistence and use a PersistentVolumeClaim instead.