Okay, to be fair, probably every Continuous Deployment technology promises to make deploying faster and allows you to deploy more often. Kelsey Hightower Why should I use GitOps? Deploy Faster More Often GitOps: versioned CI/CD on top of declarative infrastructure. It’s like having cruise control for managing your applications in production.
Cloud native java pdf size update#
If you want to deploy a new application or update an existing one, you only need to update the repository - the automated process handles everything else. The core idea of GitOps is having a Git repository that always contains declarative descriptions of the infrastructure currently desired in the production environment and an automated process to make the production environment match the described state in the repository. It focuses on a developer-centric experience when operating infrastructure, by using tools developers are already familiar with, including Git and Continuous Deployment tools.
GitOps is a way of implementing Continuous Deployment for cloud native applications. Get it as a PDF or ePub, Kindle eBook, and paperback. We’ve just released our short book on GitOps. This site aggregates the essence of GitOps to help clear up the confusion about the topic.
Since its inception in 2017 by Weaveworks, GitOps has caused quite some fuss on Twitter and KubeCon.