Document how to disable Pod antiaffinity rules (#1303)

Author: JakeSCahill

modules/deploy/pages/deployment-option/self-hosted/kubernetes/k-production-deployment.adoc

@@ -623,6 +623,19 @@ statefulset:
           topologyKey: "kubernetes.io/zone"
 ----
 
+To completely disable `podAntiAffinity` rules (for example, in development environments where you want to run multiple brokers on the same node), you can override the default configuration:
+
+[source,yaml]
+----
+statefulset:
+  podTemplate:
+    spec:
+      affinity:
+        podAntiAffinity: null
+----
+
+WARNING: Disabling `podAntiAffinity` rules is not recommended for production environments as it allows multiple brokers to be scheduled on the same node, increasing the risk of data loss if a node fails.
+
 See also: xref:./k-high-availability.adoc[]
 
 === Graceful shutdown

modules/troubleshoot/partials/errors-and-solutions.adoc

@@ -269,7 +269,7 @@ Error: UPGRADE FAILED: cannot patch "redpanda" with kind StatefulSet: StatefulSe
 ----
 
 To fix this error, include all the value overrides from the previous installation using either the `--set` or the `--values` flags.
-+
+
 WARNING: Do not use the `--reuse-values` flag to upgrade from one version of the Helm chart to another. This flag stops Helm from using any new values in the upgraded chart.
 
 === Cannot patch "redpanda-console" with kind Deployment