Why DependenciesDistributor only support ResourceBinding but not ClusterResourceBinding?

[sysucjl]

What would you like to be added:
We want that relevant resources can be propagated automatically when we progate a kind of non-namespaced resourced. So We create a dependencyInterpretation for this non-namespaced resourced, and set propagateDeps=true in ClusterPropagationPolicy，but it not work.

This seems to be because that DependenciesDistributor can only handle ResourceBinding but not ClusterResourceBinding.

karmada/pkg/dependenciesdistributor/dependencies_distributor.go

Lines 229 to 245 in 283a8a8

	func (d *DependenciesDistributor) Reconcile(ctx context.Context, request reconcile.Request) (reconcile.Result, error) {
	klog.V(4).Infof("Start to reconcile ResourceBinding(%s)", request.NamespacedName)
	bindingObject := &workv1alpha2.ResourceBinding{}
	err := d.Client.Get(ctx, request.NamespacedName, bindingObject)
	if err != nil {
	if apierrors.IsNotFound(err) {
	klog.V(4).Infof("ResourceBinding(%s) has been removed.", request.NamespacedName)
	return reconcile.Result{}, d.handleResourceBindingDeletion(request.Namespace, request.Name)
	}
	klog.Errorf("Failed to get ResourceBinding(%s): %v", request.NamespacedName, err)
	return reconcile.Result{}, err
	}
	// in case users set PropagateDeps field from "true" to "false"
	if !bindingObject.Spec.PropagateDeps || !bindingObject.DeletionTimestamp.IsZero() {
	return reconcile.Result{}, d.handleResourceBindingDeletion(request.Namespace, request.Name)
	}

Why is this needed:
DependenciesDistributor can also suport ClusterResourceBinding

[XiShanYongYe-Chang]

Hi @sysucjl, thanks for your feedback, we do not currently support cluster scope resource dependencies distributor, because for workloads, they are namespace scoped.

By the way, do you use Karmada in the product?

We want that relevant resources can be propagated automatically when we progate a kind of non-namespaced resourced.

Can you elaborate on your usage scenario?