Description of problem:

While testing MCE in QE6 cluster we discovered bad annotation in OCP cluster which comes from non OCP source repository.

Steps to Reproduce:

1. connect and login to MCE QE6 cluster
2. get the annotations for a CAPI CRD:

$ oc get crd clusters.cluster.x-k8s.io -o jsonpath='{.metadata.annotations}' | jq .
{
  "cert-manager.io/inject-ca-from": "multicluster-engine/capi-serving-cert",
  "controller-gen.kubebuilder.io/version": "v0.18.0"
}   

1. check the sources in backplane-operator repo:

 $ grep -rl multicluster-engine/capi-serving-cert ./pkg/templates/crds/cluster-api*/apiextensions.k8s.io_v1_customresourcedefinition_clusters.cluster.x-k8s.io.yaml ./pkg/templates/crds/cluster-api-k8s/apiextensions.k8s.io_v1_customresourcedefinition_clusters.cluster.x-k8s.io.yaml   

Actual results:

**

$ oc get crd clusters.cluster.x-k8s.io -o jsonpath='{.metadata.annotations}' | jq .
{
  "cert-manager.io/inject-ca-from": "multicluster-engine/capi-serving-cert",
  "controller-gen.kubebuilder.io/version": "v0.18.0"
}

Expected results:

$ oc --context crc-admin get crd clusters.cluster.x-k8s.io -o jsonpath='{.metadata.annotations}' | jq .
{
  "controller-gen.kubebuilder.io/version": "v0.18.0",
  "crd-migration.cluster.x-k8s.io/observed-generation": "5",
  "service.beta.openshift.io/inject-cabundle": "true"
} 

Additional info:

-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 1/29/26:

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

Fix or Feature Availability:
When will this be available in a build?
Code merged on: YYYY-MM-DD
Expected downstream build tag (if known): example-build-tag
(Optional) Related PR(s): Link