1. Proposed title of this feature request

Enhance MCP to Identify and Warn About Reboot-Causing Configuration Changes.

2. What is the nature and description of the request?

When a new MachineConfig is applied to a MachineConfigPool, some changes can trigger a node reboot. However, there is no built-in mechanism to alert users in advance that the change will result in node disruption.

3. Why does the customer need this? (List the business requirements here)

MCP rollout causes a reboot of the nodes. However, users may not always be fully aware that a change they are applying will cause a reboot, leading to:

• Unintended disruption of workloads.

• Eviction of pods, potential service downtime.

• Rolling reboot behaviour that may be disruptive if not planned properly.

This feature would increase operational safety, especially in production environments.

4. List any affected packages or components.

• MachineConfig

• MachineConfigController

• MachineConfigPool