Skip to content

Commit a2852d0

Browse files
Update content/operate/kubernetes/recommendations/node-selection.md
Co-authored-by: Kaitlyn Michael <76962844+kaitlynmichael@users.noreply.github.com>
1 parent 4c60c23 commit a2852d0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/operate/kubernetes/recommendations/node-selection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -196,7 +196,7 @@ If your platform doesn’t set this label automatically, you can use any custom
196196
### Node labeling requirements
197197

198198
{{< warning >}}
199-
**All eligible nodes must be labeled** with the chosen label for rack-awareness to work properly. The operator expects that all nodes where Redis Enterprise pods can be scheduled will have the specified label, and will fail and stop reconciliation if any eligible nodes are missing the label.
199+
**All eligible nodes must have the label for rack-awareness to work. The operator requires every node that might run Redis Enterprise pods to be labeled. If any are missing the label, reconciliation will fail.
200200
{{< /warning >}}
201201

202202
Eligible nodes are all nodes where Redis Enterprise pods can be scheduled. By default, these are all worker nodes in the cluster, but this can be restricted by specifying `.spec.nodeSelector` in the Redis Enterprise cluster (REC) configuration.

0 commit comments

Comments
 (0)