Description of problem: I found this issue when I verified issue https://issues.redhat.com/browse/ACM-10232 specify the node by adding addonDeploymentConfig into the managedClusterAddon or clusterManagementAddon is working. But when addonDeploymentConfig is removed from clusterManagementAddon, the specified node setting is still affected on the endpoint operator.  

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1. create one addondeploymentconfig to specify the node
2. add it into managedclsuteraddon
3. new created metrics collector running on the specified node
4. remove addondeploymentconfig from managedclsuteraddon
5. metrics collector restart and random running on one node
6. add addondeploymentconfig into clustermanagetaddon
7. metrics collector(hub)running on the specified node, endpoint operator(spoke)is pending due to there's no specified node on spoke, it's working as expected
8. remove addondeploymentconfig from clustermanagetaddon, there's no effect on hub and spoke, they still running or pending on the specified node setting in addondeploymentconfig

• metrics collector(hub) is keep running,  I delete metrics collector(hub), new one is still running on the specified node which setting in addondeploymentconfig
• endpoint operator(spoke)is still pending, I tried to delete endpoint operator(spoke), but new one still in pending.

Actual results:

Expected results:

Additional info: