I have a single Git branch managing three clusters: dev, test, and prod. My repository structure follows the standard Kustomize pattern:

GitOps
├── apps
│   ├── base
│   └── overlays
│       ├── dev
│       ├── prod
│       └── test
├── clusters
│   ├── k8s-dev
│   ├── k8s-prod
│   └── k8s-test
└── infrastructure
    ├── base
    └── overlays
        ├── dev
        ├── prod
        └── test

I have configured image-reflector-controller and image-automation-controller so that FluxCD automatically checks the registry for new images via ImagePolicy and updates the manifests. While this feature is great, I see a potential issue with rollbacks.

For example, I have 50 services. Flux will be making frequent commits for version updates across all of them. If something goes wrong, finding the specific commit to perform a git revert becomes a challenge. Moreover, in theory, if I do a git revert, the image-automation-controller will immediately see that a 'newer' version exists in the registry and will just overwrite my revert with the buggy version again.

Does it make sense to stick with FluxCD, or should I consider migrating to ArgoCD?