[OSDOCS#19352]: Clarify that multiple KubeletConfig CRs are not merged - #118856
[OSDOCS#19352]: Clarify that multiple KubeletConfig CRs are not merged#118856agawai wants to merge 1 commit into
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
|
Hi @agawai. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
|
/label merge-review-needed |
|
@agawai: The label(s) 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-sigs/prow repository. |
|
/label merge-review-needed |
Version(s):
4.21+
Issue:
https://redhat.atlassian.net/browse/OSDOCS-19352
Link to docs preview:
QE review:
Additional information:
Clarifies that multiple
KubeletConfigCRs targeting the same machine config pool are not merged. The most recently created CR takes precedence. Customers were reading the existing “multiple CRs / numeric suffix” wording as a merge.This module is included from:
machine_configuration/machine-configs-custom.adocpost_installation_configuration/node-tasks.adoc