GitOps is a methodology for automating the deployment of applications and infrastructure using Git as the single source of truth. The key principles of GitOps are: 1) The desired state is defined in a Git repo, 2) Changes are approved via pull requests, and 3) Services ensure any divergence from the desired state is corrected. GitOps advocates storing application and infrastructure code together in Git and using tools like ArgoCD to deploy updates automatically based on Git events. This push-based flow ensures deployments are fully automated, versioned, and that the deployed state matches the Git repo at all times.

2. Cloud Native CI/CD
with GitOps
Antonio Liccardi
Cloud Developer & DevOps Engineer @Blexin
Microsoft MVP for Developer Technologies
antonio.liccardi@blexin.com
@turibbio

3. Agenda
• GitOps definition
• DevOps & GitOps
• GitOps principles
• Tools & best practices

4. What is GitOps?

5. GitOps principles
• The entire system is described by using a declarative
approach. The desired state of the system is versioned
in a Git repository
• The changes need to be approved, and they are
automatically applied to the system
• Services will guarantee the application of the desired
state and alert in case of divergence

6. GitOps in practice
• Git is the single source of truth, any change in git will
trigger all the operations
• Both the application and the infrastructure are stored in
the Git repository. Using tools such as kubectl to apply
a configuration is not suggested (Self-documenting
Deployments)
• Once prepared the workflow, the entire process is
guided by pull requests, and it is fully automated

7. GitOps in a sentence
Only what can be described and observed
can be automated and controlled

8. GitOps & DevOps
• GitOps is mainly based on DevOps
• Why now?
– Until today, there were only a few frameworks able to create an
infrastructure in a declarative way to be stored in Git
– Git is the best tool to store an infrastructure thanks to auditing,
comments and review feature

9. GitOps advantages
Increased
productivity
Better developer
experience
Compliance &
Stability
(audit)
Higher Reliability
(MTTR)
Consistency and
standardization
(workflow)
Stronger
Security
Guarantees

10. 3 GitOps pillars
Pipelines Observability Control

11. Pipeline: Push-based approach

12. Pipeline: Push-based approach

13. Pipeline: Pull-based approach

14. Pipeline: Pull-based approach

15. Multiple environments

16. Observability
• It is hard to find a problem in our system if it is not
observable

17. Observability

18. Control
Works
closely with
Observability
Controls
means
Convergence

19. Control

20. GitOps Lifecycle

21. A GitOps repository

22. A GitOps repository
• 1 repository per application, 1 repository for environment
configuration
• Branches are mapped to environments
• Changes are related to both application code and
infrastructure
• Rollback using revert
• Use of protected branches to force the pull request

23. DEMO
GitOps, K8s, Azure DevOps & ArgoCD

24. Is GitOps the right approach
for me?

26. Questions? Thoughts?
Antonio Liccardi
Cloud Developer & DevOps Engineer @Blexin
Microsoft MVP for Developer Technologies
antonio.liccardi@blexin.com
@turibbio

27. Resources
• https://www.gitops.tech/
• https://www.weave.works/technologies/gitops/
• https://www.weave.works/blog/what-is-gitops-really
• https://www.youtube.com/watch?v=BSqE2RqctNs