From 57a3b72cdedb38240d9c776bf2347ed520023e67 Mon Sep 17 00:00:00 2001
From: Mike Green <772413+mikegreen@users.noreply.github.com>
Date: Wed, 8 Jan 2020 17:09:41 -0700
Subject: [PATCH] Docs: Add note about needing to do plugin reload on each node
 (#8108)

* Add note about needing to do this on each node

Specifically calling this out will heed off operators doing this on a single node and thinking it is a bug that it didn't propagate to the other nodes, secondaries, etc.

* Updated to reflect not needing to do registration on each
---
 website/source/docs/upgrading/plugins.html.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/website/source/docs/upgrading/plugins.html.md b/website/source/docs/upgrading/plugins.html.md
index 775a356e4..921378c68 100644
--- a/website/source/docs/upgrading/plugins.html.md
+++ b/website/source/docs/upgrading/plugins.html.md
@@ -35,4 +35,9 @@ with either the `plugin` or `mounts` parameter respectively.
 Until step 4, the mount will still use plugin_v1, and when the reload is
 triggered, Vault will kill plugin_v1’s process and start a plugin_v2 process.
 
-[plugin_reload_api]: /api/system/plugins-reload-backend.html
\ No newline at end of file
+-> **Important:** Plugin reload of a new plugin binary must be 
+performed on each Vault instance. Performing a plugin upgrade on a single 
+instance or through a load balancer can result in mismatched 
+plugin binaries within a cluster. 
+
+[plugin_reload_api]: /api/system/plugins-reload-backend.html