The current PerformanceProfile cluster-compare logic assumes there will be a "NodeSelector" that can be used to lookup the nodes associated with the PerformanceProfile and detect the CPU architecture.  However, this logic is incomplete.  "NodeSelector" is optional, and users may legitimately use "MachineConfigLabels" or "MachineConfigPoolSelector" instead, to link the PerformanceProfile to a group of nodes.

4.20

100%, but only if customers deviate from our example PerformanceProfile which does set a NodeSelector.

    1. Establish a PerformanceProfile from the RAN RDS without a NodeSelector, but using a MachineConfigPoolSelector instead
    2. Run cluster-compare with the RAN RDS templates

The PerformanceProfile architecture detection logic fails to find the CPU architecture:

The PerformanceProfile architecture detection logic should succeed and detect the CPU architecture.