The Path to GitOps
Get the e-book
GitOps delivers on the vision promised to a DevOps culture, and while the practice isn’t new, organizations are starting to realize how valuable it is to deliver products in a fast, highly automated, and secure way— without compromising the quality of their code. This book outlines the tools, workflows, and structures that teams need to have in place to enable a complete GitOps workflow for practitioners who are just getting started or considering developing their own GitOps practice.
- Learn how GitOps relates to the DevOps movement and examine the foundational GitOps principles defined by the OpenGitOps Sandbox project
- Discover best practices for structuring Git workflows for your deployments
- Understand where GitOps fits in your CI/CD (continuous integration/continuous delivery) pipelines and explore the various ways you can implement it
- Explore Argo CD, Flux, and other popular tools used to manage GitOps workflows, and see how Kustomize, Helm, and Kubernetes Operators help minimize the management of lengthy configuration files
- Get tips for setting up policies and security for your Git workflows
About the author
Christian Hernandez spent eight years on the customer and field engagement team in Red Hat’s Hybrid Platforms organization and hosted the biweekly GitOps Guide to the Galaxy. He is now is a product manager for Red Hat cloud services offerings. A contributor to Argo CD and OpenGitOps, Christian is a technologist with experience in infrastructure engineering, systems administration, enterprise architecture, tech support, advocacy, and management. Lately, he has been focusing on Kubernetes, DevOps, cloud-native architecture, and GitOps practices. Christian is passionate about open source and containerizing the world one application at a time.
GitOps doesn’t replace CI/CD, but participates in it. While traditional tools like Jenkins and CloudBees focus on the entire CI/CD process, GitOps focuses on the CD aspect (both continuous deployment and continuous delivery). So now, instead of having deployment of your application be imperative in your CI/CD platform, it can be declarative based on a source of truth. Based on a reconciliation loop, the GitOps controller makes changes to the cluster by deploying new instances, once those changes have been committed to the state store.