Currently, the function for determining the MachineConfigPool (MCP) a node is a part of (`GetPrimaryPoolNameForMCN`) is called as needed throughout the MachineConfigOperator's (MCO's) update functions and then passed into the MachineConfigNode (MCN) update functions (`GenerateAndApplyMachineConfigNodes` and `GenerateAndApplyMachineConfigNodeSpec`) as needed. This pattern was implemented as part of MCO-1501.

This story involves updating the pattern described to move the pool determination functionality (`GetPrimaryPoolNameForMCN`) into the MCN generation functions (`GenerateAndApplyMachineConfigNodes` and `GenerateAndApplyMachineConfigNodeSpec`) and then cleaning up code where applicable.

Done when:

• MCP association is determined within the MCN generation functions
• Code is cleaned up as needed
• Extra line mentioned in MCO-1501 PR is removed

References:

• PR where custom MCP support was first implemented
• Comment with information on desired design pattern update