During deploying loadtester via flux, "kustomization path not found" appears

[kwongtn]

Describe the bug

Following tutorial at flagger website, I tried to deploy loadtester with the following configuration (everything is the same except with namespace).

apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: OCIRepository
metadata:
  name: flagger-loadtester
  namespace: flagger-system
spec:
  interval: 6h # scan for new versions every six hours
  url: oci://ghcr.io/fluxcd/flagger-manifests
  ref:
    semver: 1.x # update to the latest version
  verify: # verify the artifact signature with Cosign keyless
    provider: cosign
---
apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
kind: Kustomization
metadata:
  name: flagger-loadtester
  namespace: flagger-system
spec:
  interval: 6h
  wait: true
  timeout: 5m
  prune: true
  sourceRef:
    kind: OCIRepository
    name: flagger-loadtester
  path: ./kustomize/tester
  targetNamespace: flagger-system

However on deploy it shows: ArtifactFailed: kustomization path not found: stat /tmp/kustomization-878691743/kustomize/tester: no such file or directory

If I delete spec.path from the Kustomization file, it shows: BuildFailed: kustomize build failed: accumulating resources: accumulation err='accumulating resources from './appmesh': read /tmp/kustomization-2874416656/appmesh: is a directory': recursed merging from path '/tmp/kustomization-2874416656/appmesh': may not add resource with an already registered id: ClusterRole.v1.rbac.authorization.k8s.io/flagger.[noNs]

Help?

Additional context

• Flagger version: 1.29.0
• Kubernetes version: 1.25.4
• Service Mesh provider: None
• Ingress provider: None (I think)