Section Number and Name:
Understanding the Machine Config Operator
Describe the issue:
As MCO design of 4.x, configuration changes will cause nodes reboots. We understand it's the current design, and if nodes are adopted with HA, it should cause no service downtime. But any automated reboot is considered a big impact in China. So what our request is: Can we add a big&bold warning in the documentation to warn customers of the auto reboots so that they will be aware of this and get better prepared for this.
To share more background, many customers in China don't know about auto reboots triggered by MCO, so sometimes they were surprised by the attack. This has caused concern among many China customers. Thus we need a warning which is easier for customers to catch.
This request is targeted to all 4.x versions.
You filed a similar BZ  which is being addressed by another writer. Does this warning cover your concerns here? 
"To prevent control plane nodes from autorebooting after machine config changes are applied, you must pause the autoreboot process by setting the `spec.paused` field to `true` in the machine pool config."
I added the first sentence to the note I mentioned in comment 2:
Changes to the machine configuration cause automatic nodes reboots.
To prevent control plane nodes from autorebooting after machine config changes are applied, you must pause the autoreboot process by setting the `spec.paused` field to `true` in the machine pool config.
Please take a look. Thank you.
This is Judith. Thanks a lot for your support on this bug.
We see that the product documentation has been updated(https://docs.openshift.com/container-platform/4.6/architecture/control-plane.html#understanding-machine-config-operator_control-plane). however, the sentence "Changes to the machine configuration cause automatic nodes reboots." is missing ? Can you pls also include that ? It's also important.
Also, after "you must pause the autoreboot process by setting the `spec.paused` field to `true` in the machine pool config.", can we add something like "Please refer to the section of "Disabling Machine Config Operator from automatically rebooting (https://docs.openshift.com/container-platform/4.6/support/troubleshooting/troubleshooting-operator-issues.html#troubleshooting-disabling-autoreboot-mco_troubleshooting-operator-issues)""? It will make customers easier to understand how to pause/unpause.
I added a reference to the "Disabling Machine Config Operator from automatically rebooting" section (we are not allowed to add links to the docs at the level where the note is). However, this section was added in 4.5 and does not appear in 4.4; also, the `spec.paused` field is not mentioned in the 4.4 docs.
Would it be acceptable to make these changes in 4.5+?
Hi Michael, Please go ahead. Thank you for your quick actions!
I commented on the PR and tagged some MCO folks for additional input.