regen known-issue-rhidp-5342 using ./modules/release-notes/single-source-release-notes.py

Signed-off-by: Nick Boldt <[email protected]>

Author: nickboldt

modules/release-notes/ref-release-notes-known-issues.adoc

@@ -7,11 +7,12 @@ This section lists known issues in {product} {product-version}.
 [id="known-issue-rhidp-5342"]
 == [Helm] Cannot run two RHDH replicas on different nodes due to Multi-Attach errors on the dynamic plugins root PVC
 
-If you are deploying {product-short} using the Helm Chart, it is currently impossible to have 2 replicas running on different cluster nodes. This might also affect the upgrade from 1.3 to 1.4.0 if the new pod is scheduled on a different node.
+Currently, when deploying {product-short} using the Helm Chart, two replicas cannot run on different cluster nodes. This might also affect the upgrade from 1.3 to 1.4.0 if the new pod is scheduled on a different node.
 
-A possible workaround for the upgrade is to manually scale down the number of replicas to 0 before upgrading your Helm release. Or manually remove the old {product-short} pod after upgrading the Helm release. However, this would imply some application downtime.
-You can also leverage a Pod Affinity rule to force the cluster scheduler to run your {product-short} pods on the same node.
-
+Possible workarounds for the upgrade include the following actions:
+* Manually scale down the number of replicas to 0 before upgrading your Helm release. 
+* Manually remove the old {product-short} pod after upgrading the Helm release. However, this would imply some application downtime.
+* Leverage a Pod Affinity rule to force the cluster scheduler to run your {product-short} pods on the same node.
 
 .Additional resources