I am installing the ACM operator and then create a MCH resources keeping the defaults ( I am not making any changes to the predefined settings )

Once the MCH resource is created, I can see the spec > enableClusterBackup option set to false. This option has been deprecated for a while, replaced by the overrides> components > cluster-backup

Since it is deprecated, we should not create it on the MCH resource. I am questioning if we can completely remove from the CRD since I think it's been a while since it was marked as deprecated.

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 10/22/25:

Summary of the Work:
What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.
e.g., "Updated the UI to show validation errors for the form. The previous implementation did not surface backend validation issues."

Key Areas to Verify:

1. What functionality should QE focus on? List what was tested or what is most important to validate.
2. Ensure the new validation messages appear for required fields
3. Confirm the workflow still completes as expected after validation fixes
4. Any edge cases or high-risk areas touched by the change

• When generating the MCH CR for ACM 2.15, the enableClusterBackup field should not appear in a fresh installation. This field is deprecated and should not be included by default.

apiVersion: operator.open-cluster-management.io/v1
kind: MultiClusterHub
metadata:
  name: multiclusterhub
  namespace: open-cluster-management
spec:
  availabilityConfig: High
  enableClusterBackup: false <- should not be set.
  ingress: {} <- should not be set.
  localClusterName: local-cluster 

Fix or Feature Availability:
When will this be available in a build?
Code merged on: 2025-10-22
Expected downstream build tag (if known): Next available 2.15 image.
(Optional) Related PR(s): https://github.com/stolostron/multiclusterhub-operator/pull/2803