Chapter 5: The Purist GitOps – Continuous Deployment Everywhere
The second school of thought can be categorized as purist. By adhering to the basic tenants of what makes GitOps beneficial, the purist mindset is broader in scope than the originalist school is.
As we mentioned in an earlier chapter, storing configuration code in a central source code manager is nothing new. But what makes GitOps, and especially purist GitOps, different from traditional practices is using source code management systems as a source of truth.
In this chapter, we're going to cover the following main topics:
- Purist GitOps basics
- Servers, containers, and serverless deployment as code
- Declarative files overload
- Benefits and drawbacks of purist GitOps
- Common purist GitOps tools
Let's get started!