Clusters upgraded from 4.1 will have the old credentials secret left over. This was renamed between 4.1 and 4.2 to allow for different credentials requests for different platforms, but by being left over has caused issues for customers when they have upgraded and we have added new permissions. CCO was targeting the same secret for two different CredentialsRequests.

Ref: https://github.com/openshift/machine-api-operator/blob/545465beeeb6d99fd890c6b3bc5dba5789a38b4c/install/0000_30_machine-api-operator_00_credentials-request.yaml#L6

We need to clean these up once CVO implements the ability to remove resources.

To remove the object, we will need to add the manifest back and ensure it has `release.openshift.io/delete: "true"` as an annotation, this will force CVO to delete it on a cluster if it exists.

DoD:

• When a cluster is upgraded to 4.9, if the legacy credentials request exist, it will be removed

Docs:

• This should be called out in the release notes