Hi @Patrick Cornelissen (DPDHL IT Services), external ,
Thanks for reaching out to Microsoft QnA.
Can you check the below latest documentation on multi-tenancy feature : https://learn.microsoft.com/en-us/azure/azure-arc/kubernetes/tutorial-use-gitops-flux2#multi-tenancy.
The issue may be related.
Let me know if this helps? Meanwhile, I am trying to check more on this.
I did check internally with the Team. Yes, this is related to the multi-tenancy fix that was recently released.
We don’t recommend that you remove those flags, since it means that the “namespaced” scoped configurations would not actually be namespaced (in the sense that anyone who has write-access to that namespace (even if they don’t have write access to other namespace) can actually deploy anything across the cluster).
Ideally, the workaround for this issue is to deploy your HelmRelease to the same namespace as the configuration so that the reconciliation all resides in that namespace with elevated privilege. This means you will have to set the “targetNamespace” on the HelmRelease to specify the namespace that you want to deploy the chart to.
Hope this helps.
Accept as Answer and
Upvote if you think the information provided was useful.