Hello everyone, what I am reporting below is a misadventure I faced a few months ago but on which I have not yet found a definitive and clear answer.

On a development AKS (Azure Kubernetes Service) cluster on which I bootstrapped Flux v2.3.0, I encountered a problem following the push of a file with the name 'kustomization.yaml', on the GitRepository synchronized by Flux, where HelmReleases and other k8s yaml manifests are present for the synchronization.

Searching among other issues, I know that there should be a single file with the name 'kustomization.yaml', but I did this because this is what the ExternalSecret documentation for secret management required, as you can see at the following link, under the section Create the main kustomization.

After the push of incriminated file, the entire FluxCD installation disappeared, including obviously the released resources.

Why does this happen? How is it possible that FluxCD self-destructs from the cluster? How can this be prevented?
And how should I behave if I were to unfortunately find myself facing this problem to restore everything?

I thank anyone who will help me find the answers to these questions of mine.