What happened:
I have two yaml config of resourceregistry,they just namespace different

apiVersion: search.karmada.io/v1alpha1
kind: ResourceRegistry
metadata:
  name: secret-search-ns1
spec:
  targetCluster:
    clusterNames:
      - cluster-1
  resourceSelectors:
    - apiVersion: v1
      kind: Secret
      namespace: ns1

apiVersion: search.karmada.io/v1alpha1
kind: ResourceRegistry
metadata:
  name: secret-search-ns2
spec:
  targetCluster:
    clusterNames:
      - cluster-1
  resourceSelectors:
    - apiVersion: v1
      kind: Secret
      namespace: ns2

when I apply them ,karmada-search just cached one namespace resource,the latter one override the previous one namespace
get ResourceRegistry:

get secret,juet get ns1's secret:

What you expected to happen:
I think karmada-search should merge these namespace,
it should cached ns1 and ns2,this should be a bug.
How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Karmada version: 1.12.2
• kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version):
• Others: