How was observability ensured in GitOps? How to ensure that the correct version was deployed without errors?

In GitOps observability is ensured through integration with monitoring and logging systems, as well as automated deployment status checks.

Main approaches:

• Using tools for cluster state management, such as Argo CD or Flux, which track the compliance of the current cluster state with the desired state described in Git.
• Monitoring metrics and logs with Prometheus, Grafana, ELK Stack, or Loki. This allows seeing how the application is functioning after deployment.
• Automatic notifications in case of errors or deviations.
• Checking release status via CLI or UI tools of GitOps, where you can see which version of the application is deployed and whether all stages have passed successfully.

Thus, to ensure that the correct version has been deployed without errors, they look at:

• The synchronization status of the GitOps tool (for example, Argo CD shows "Synced" and "Healthy").
• Application logs and metrics for errors.
• Automated tests and checks after deployment.

Example command to check status in Argo CD:

argocd app get <app-name>

It will show the current version, synchronization status, and application health.