trident unit creates Secrets and TridentBackendConfig in wrong namespace

Summary

when you deploy trident unit, it creates secrets and tbc in wrong namespace i.e. sylva-system while it should use trident namespace.

What is the expected correct behavior?

tbc and secrets should use trident nemespace

Relevant logs and/or screenshots

kubectl get tbc -A
NAMESPACE      NAME                    BACKEND NAME   BACKEND UUID   PHASE   STATUS
sylva-system   backend-tbc-ontap-nas
sylva-system   backend-tbc-ontap-san

kubectl get secret -n sylva-system
NAME                                           TYPE                 DATA   AGE
backend-tbc-ontap-nas-secret                   Opaque               2      11h
backend-tbc-ontap-san-secret                   Opaque               6      11h