From 67ed2cfc1ec4bca37214534166111df77b9d9e0c Mon Sep 17 00:00:00 2001
From: John Iacona <john.iacona@gmail.com>
Date: Wed, 18 Oct 2017 16:06:14 +0100
Subject: [PATCH] Update using_helm.md

Add explanation of persistence behavior of `--set`
---
 docs/using_helm.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/using_helm.md b/docs/using_helm.md
index 77e4cffc2..6bf3b2bcc 100755
--- a/docs/using_helm.md
+++ b/docs/using_helm.md
@@ -230,6 +230,10 @@ There are two ways to pass configuration data during install:
 - `--set`: Specify overrides on the command line.
 
 If both are used, `--set` values are merged into `--values` with higher precedence.
+Overrides specified with `--set` are persisted in a configmap. Values that have been
+`--set` can be viewed for a given release with `helm get values <release-name>`. 
+Values that have been `--set` can be cleared by running `helm upgrade` with `--reset-values`
+specified.
 
 #### The Format and Limitations of `--set`