-
Bug
-
Resolution: Done
-
Minor
-
DO380 - OCP4.14-en-1-20240220, DO380 - Early Access
-
None
-
False
-
-
False
-
3
-
-
-
en-US (English)
Please fill in the following information:
| URL: | https://role.rhu.redhat.com/rol-rhu/app/courses/do380ea-4.14/pages/ch03 |
| Reporter RHNID: | |
| Section Title: | h2. Node Pools |
Issue description
Heading "Node Labels" only mention manually adding labels directly to nodes, and mistakenly states that applies to "user-provisioned infrastructure" (UPI). It fails to mention that, if a cluster was installed with a Kubernetes cloud provider enabled (which also includes VMware, OpenStack, and the Bare Metal operator) you must set labels though a machineset.
It is incorrect because UPI clusters can also be installed with a cloud provider enabled and them you should not set labels on nodes directly, because those labels can be overriden by the machine API or cluster API when they recrete or recreate nodes.
See for information about the need to scale down or somehow recreate nodes when setting labels using a machine set, this should be a reference link in the lecture.
https://access.redhat.com/solutions/6955894
Steps to reproduce:
Workaround:
Expected result: