1. Proposed title of this feature request

PAO as stand alone feature not tied to the name of the MCP

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

Right now, when configuring identical hardware for different configuration in the same cluster (e.g. different node CIDR, different VLANs configs, different maintenance/upgrade windows, etc, the nodes are aggregated on MCPs. With the one PAO per MCP it becomes an operational burden to maintain this.

The asks is for making it so that a PAO profiles can be applied to any number of MCPs by applying a label to it or by having the MCPs consume a particular common MC definition. For example, applying a label "example.com/pao-profile-1" or having an MC that advertises to a label eg. "machineconfiguration.openshift.io/role: pao-profile-1" which can be consumed by multiple MCPs like

```
—
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfigPool
metadata:
labels:
custom-kubelet: max-pods-500
name: ran-du-abc01
spec:
machineConfigSelector:
matchExpressions:

• { key: machineconfiguration.openshift.io/role, operator: In, values: [worker, pao-profile-1, ran-du] }

```

4. List any affected packages or components.

Performance-addon-operator