1. Proposed title of this feature request
   • Add "Drain Node" action in the OpenShift Web Console
2. What is the nature and description of the request?
   • The request proposes adding a new user action, "Drain Node for Maintenance," to the action menu (kebab menu) for each node on the Compute > Nodes page. This action would safely prepare a node for maintenance by cordoning it and evicting its workloads.

                     The proposed workflow is as follows:

                        - An administrator selects the action from the node's menu.

                        - A confirmation dialog appears, explaining that the node will be made unschedulable and all eligible pods will be terminated and moved to other nodes. This dialog should also clarify how resources like DaemonSets and pods with local storage (ˇ) will be handled (e.g., by defaulting to ignore daemonsets and delete ˘ data).

                        - Upon confirmation, the console backend executes the equivalent of `oc adm drain <node_name>`.

                        - The UI provides clear feedback on the drain's progress.

                        - Once complete, the node is left in a `Ready`, `SchedulingDisabled` state, free of workloads and ready for the administrator to perform manual maintenance (e.g., hardware checks, debugging, or a planned shutdown).

                        - Crucially, this action does not automatically uncordon the node. 

1. Why does the customer need this? (List the business requirements here)
   • This feature supports critical business needs for safe and efficient cluster maintenance.

                        - Improve Service Reliability.

                        - Increase Operational Efficiency.

                        - Enable Controlled Maintenance Workflows.

                        - Reduce Skill Threshold for Maintenance.

1. List any affected packages or components.
   • OpenShift Web Console