What problem are you facing?

I'm trying to use the namespaced release but the provider is creating the release in a different namespace from the deployment.

I have a release.helm.m.crossplane.io object for external secrets manager in a "hub" cluster in a namespace called ty. The release.helm.m.crossplane.io is using a provider config with a kubeconfig secret for a remote cluster called "test-cluster". I would like the release secret and external secrets manager to be created in the external-secrets namespace on the remote cluster. However, everything is created in the ty namespace on the remote cluster which doesn't exist.

How could Crossplane help solve your problem?

I would like an option similar to the spec.forProvider.namespace field in the cluster scoped release add to the namespace scoped release ( or an equivalent to helm install -n external-secrets)?