What does Velero add when using managed Kubernetes services?

I understand why Velero can be useful, but I'm not convinced it adds much beyond another system to operate when running a managed Kubernetes cluster such as EKS, AKS, or GKE. Assume the cluster hosts both stateless and stateful applications, excluding databases that are already managed by a service such as RDS. GitOps tools like Flux or Argo CD can rebuild application resources and support migrations or A/B deployments, while provider-managed volume snapshots can protect persistent data. In that setup, what specific problem does Velero solve? Does it make disaster recovery, incident response, or cluster upgrades meaningfully easier, or is it mostly redundant?