Why GitOps ?

What is GitOps?

GitOps is an approach to using a version control/source control system as a single source of truth for all infrastructure and configuration.

Just keep it in your mind, GitOps is a philosophical approach so it’s not something special to just Kubernetes or containers.

Why we need it?

GitOps is a philosophical that uses Git as a single source of truth, since we use git for all modification so it’s much easy to rollback if we found any failure.

• Single Source of Truth: The first and most important principle of GitOps. It states Git is always right. You can understand the whole system just by looking at Git because it has all the ingredients right there.
• Everything as a Code: It states everything should be kept in the form of code be it the application or any other component which application needed. In most cases, infrastructure is also defined in the form of code. For example:- Cloud Instance, Docker containers, Kubernetes Deployments.
• Modular architecture
  GitOps has three parts: the Git repo, the deployment process, and possibly a process that automates version updates in the Git repo. All three of these can evolve or be replaced independently of each other.
• CI/CD : This part is more interesting. Build, Test and Deploy will happen automatically relying on the truth in the repository. Infrastructure creation and application deployment will be part of this according to the infrastructure and configuration as a code.

Conclusion

Some believe GitOps may be the future of DevOps — this is because GitOps is both a declarative and a cloud-native approach to configuration management. GitOps is certainly useful in instances where using version control to manage infrastructure and application deployment would be difficult otherwise.However GitOps may not be the right fit for everyone,as not every organization will view having a reliance on a single tool, these tools get matured, GitOps implementation would be much easier.