Description of problem:

If you have DiscoveryConfig created and then try to disable the component in the MCE via the UI, you will see this error:

admission webhook "multiclusterengines.multicluster.openshift.io" denied the request: existing DiscoveryConfig resources must first be deleted

This is expected and good. However, if you try to use the CLI and disable the component, there will be a duplicate entry for discovery in the MCE yaml and the MCE component will be stuck in Progressing forever. The component will not get disabled.

oc patch mce multiclusterengine -p '[{"op": "add", "path": "/spec/overrides/components/-","value":{"name":"discovery","enabled":false}}]' --type=json

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

2.15

How reproducible:

Always

Steps to Reproduce:

1. Install ACM/MCE
2. Create a DiscoveryConfig
3. Disable Discovery in the MCE

Actual results:

Described above

Expected results:

It should get disabled