From db6c5d1b20a34ce3223a882f8865053c42c2dcaa Mon Sep 17 00:00:00 2001
From: Rebecca Zanzig <rzazzl@hotmail.com>
Date: Thu, 8 Nov 2018 12:07:30 -0800
Subject: [PATCH] Add doc info for added server affinity value

Supports newly added functionality to the Helm chart.
---
 website/source/docs/platform/k8s/helm.html.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/website/source/docs/platform/k8s/helm.html.md b/website/source/docs/platform/k8s/helm.html.md
index 17e4cdd005..47ada433b3 100644
--- a/website/source/docs/platform/k8s/helm.html.md
+++ b/website/source/docs/platform/k8s/helm.html.md
@@ -194,6 +194,13 @@ and consider if they're appropriate for your deployment.
       configuration files from this volume with `-config-dir`. This defaults
       to false.
 
+  - <a name="v-server-affinity" href="#v-server-affinity">`affinity`</a> (`string`) -
+  This value defines the [affinity](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity)
+  for server pods. It defaults to allowing only a single pod on each node,
+  which minimizes risk of the cluster becoming unusable if a node is lost.
+  If you need to run more pods per node (for example, testing on Minikube),
+  set this value to `null`.
+
 * <a name="v-client" href="#v-client">`client`</a> - Values that configure
   running a Consul client agent on Kubernetes nodes.