Enabling cross-namespace references on flux and Azure AKS / gitops

Trying to add a nginx ingress controller (amongst other things) to my Azure AKS cluster and running into the following issue when trying to deploy via the MS flux v2 gitops setup. Think it's related to the flux/aks side of things but not too sure on where to start to enable the cross-namespace setting.

Anyone any ideas?

[
    {
        "lastTransitionTime": "2022-07-08T14:43:57+00:00",
        "message": "can't access  cross-namespace references have been blocked",
        "reason": "AccessDenied",
        "status": "False",
        "type": "Ready"
    }
]

trying to deploy using this helm manifest setup:

apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: HelmRepository
metadata:
  name: ingress-nginx
  namespace: flux-system
spec:
  interval: 30m
  url: https://kubernetes.github.io/ingress-nginx

apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: ingress-nginx
  namespace: ingress-system
spec:
  interval: 5m
  chart:
    spec:
      chart: ingress-nginx
      version: '4.0.13'
      sourceRef:
        kind: HelmRepository
        name: ingress-nginx
        namespace: flux-system
      interval: 1m

Read network policies being mentioned on my cluster but not seeing anything that looks relevant. Maybe just me!!

Anyone any tips? Thank you

From the error message, it looks like you bootstrapped your Flux installation with the following flag: --no-cross-namespace-refs=true.

Note that on multi-tenant clusters, platform admins can disable cross-namespace references with the --no-cross-namespace-refs=true flag. When this flag is set, the helmrelease can only refer to sources in the same namespace as the helmrelease object.

Reference: https://fluxcd.io/docs/components/helm/helmreleases/#helm-chart-template