enhancement request: Specify the target cluster for the fluxcd resources themselves (in addition to kubeConfig.secretRef)

[ToterKojote]

Hi all,

we are using fluxcd to apply resources against remote clusters which do not have flux installed (using kubeConfig.secretRef in the kustomize.toolkit.fluxcd.io and helm.toolkit.fluxcd.io resources).

But this leads to problems if we put all the resources for a remote cluster beneath the same folder path.
I'll try to keep the example as simple as possible.

Given the following folder structure:
remote-cluster/
├─ helm_release.yaml
├─ namespace.yaml
├─ kustomization.yaml

A fluxcd kustomize.toolkit.fluxcd.io resource is applying all resources beneath the remote-cluster folder to a remote cluster.
But if the helm_release.yaml file is kind of helm.toolkit.fluxcd.io it cant be applied against the remote cluster since flux is not installed there. This forces us to move the helm_release.yaml to another folder that is not beneath the remote-cluster folder.
In the given example this would not be much of a problem but if the folder structure is more complex this could lead to a very confusing structure.

So in addition to the kubeConfig.secretRef field, that specifies to which cluster the processed resources will be applied, it would be very helpful to have a field that specifies the cluster the flux resource itself will be applied to. This would make folder structure design for remote-clusters much easier.