NTO: More precise description of MCP matching.#30905
NTO: More precise description of MCP matching.#30905ahardin-rh merged 1 commit intoopenshift:masterfrom
Conversation
The documentation was not precise when it came to two or more MachineConfigPools with nodeSelector matching the same node(s). This can happen (e.g. when a node has both master and worker role), but a single node will always be assigned (a member of) only one or no MachineConfigPool.
openshift-ci-robot
added
the
size/XS
|
/cc @ahardin-rh |
|
Deploy preview for osdocs ready! Built with commit c16f796 |
|
@skordas any chance you could provide QE review for this one? Thanks! |
|
/lgtm |
|
/cherrypick enterprise-4.6 |
|
/cherrypick enterprise-4.7 |
|
/cherrypick enterprise-4.8 |
|
@ahardin-rh: new pull request created: #31299 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@ahardin-rh: new pull request created: #31300 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@ahardin-rh: new pull request created: #31301 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
5 participants
The documentation was not precise when it came to two or more
MachineConfigPools with nodeSelector matching the same node(s). This
can happen (e.g. when a node has both master and worker role), but a
single node will always be assigned (a member of) only one or no
MachineConfigPool.