Fix reference on how pod anti-affinity can be disabled

Jonathan S. Katz · Jonathan S. Katz · commit aeab02b4fb77 · 2019-12-30T11:22:42.000-06:00
It's `disabled` not `none`.
diff --git a/hugo/content/architecture/high-availability.md b/hugo/content/architecture/high-availability.md
@@ -169,7 +169,7 @@ it will not schedule the pod until a different node is available. While this
 guarantees that no pod will share the same node, it can also lead to downtime
 events as well. This uses the `requiredDuringSchedulingIgnoredDuringExecution`
 affinity rule.
-- `none`: Pod Anti-Affinity is not used.
+- `disabled`: Pod Anti-Affinity is not used.
 
 With the default `preferred` Pod Anti-Affinity rule enabled, Kubernetes will
 attempt to schedule pods created by each of the separate deployments above on a
