Skip to content

Commit 098e91f

Browse files
author
GitHub Actions
committed
Update RN texts
1 parent 93e35a9 commit 098e91f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Permissions associated only with front-end plugins do not appear in the UI becau
1616
[id="known-issue-rhidp-5342"]
1717
== Unable to run two {product-very-short} replicas on different nodes due to Multi-Attach errors on dynamic plugins root PVC
1818

19-
If you are deploying {product-short} using the Helm Chart, it is currently impossible to have two 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.
19+
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.
2020

2121
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.
2222

0 commit comments

Comments
 (0)