Currently MachineConfiguration is only effective with name cluster, we can create multiple MachineConfigurations with other names like

apiVersion: operator.openshift.io/v1
kind: MachineConfiguration
metadata:
  name: ndp-file-action-none
  namespace: openshift-machine-config-operator
spec:
  nodeDisruptionPolicy:
    files:
      - path: /etc/test
        actions:
           - type: None

But only 'cluster' can take action, it will make the user confused

always

Create MachineConfiguration with any name expect 'cluster'     

new MachineConfiguration won't be effective

if the function only works with 'cluster' object, we should reject the CR creation with other names