You're reading from Modern DevOps Practices Implement and secure DevOps in the public cloud with cutting-edge tools, tips, tricks, and techniques

Product type Paperback

Published in Sep 2021

Publisher Packt

ISBN-13 9781800562387

Length 530 pages

Edition 1st Edition

Tools

Docker

Concepts

Continuous Delivery

Author (1):

Gaurav Agarwal

View More author details

Table of Contents (19) Chapters

Preface

1. Section 1: Container Fundamentals and Best Practices

2. Chapter 1: The Move to Containers FREE CHAPTER

3. Chapter 2: Containerization with Docker

4. Chapter 3: Creating and Managing Container Images

5. Chapter 4: Container Orchestration with Kubernetes – Part I

6. Chapter 5: Container Orchestration with Kubernetes – Part II

7. Section 2: Delivering Containers

8. Chapter 6: Infrastructure as Code (IaC) with Terraform

9. Chapter 7: Configuration Management with Ansible

10. Chapter 8: IaC and Config Management in Action

11. Chapter 9: Containers as a Service (CaaS) and Serverless Computing for Containers

12. Chapter 10: Continuous Integration

13. Chapter 11: Continuous Deployment/Delivery with Spinnaker

14. Chapter 12: Securing the Deployment Pipeline

15. Section 3: Modern DevOps with GitOps

16. Chapter 13: Understanding DevOps with GitOps

17. Chapter 14: CI/CD Pipelines with GitOps

18. Other Books You May Enjoy

The branching strategy and GitOps workflow

GitOps requires at least two kinds of Git repositories to function: the application repository from where your builds are triggered and the environment repository that contains all of the infrastructure and configuration as code. All deployments are driven from the environment repository, and the changes to the code repository drive the deployments. GitOps follows two primary kinds of deployment models: the push model and the pull model. Let's discuss each of them.

The push model

The push model pushes any changes that occur within your Git repository to the environment. The following diagram explains the process in detail:

Figure 13.1 – The push model

The push model is inherently unaware of the existing configuration and reacts only to changes made to your Git repositories. Therefore, you will need to set up some form of monitoring to understand whether there are any deviations. Additionally, the...