Environments Based On Pull Requests (PRs): Using Argo CD To Apply GitOps Principles On Previews

Release frequency keeps increasing and, with it, the need to get away from static environments like staging, integration, and other permanent setups. Dynamic environments based on pull requests are probably the best example of a need for a much higher level of dynamism. Kubernetes allows us to easily create whatever we need, and destroy what is not in use. There is no need for anything, especially not environments to be permanent, except for production. We can get far in that direction by combining GitOps practices and Argo CD in a way that each pull request (PR) creates a new environment that is destroyed when a PR is closed. By doing that, we can improve efficiency while, at the same time, reducing the costs.
Timecodes:
00:00 Intro
03:49 Helpful resources
04:48 Creating initial resources
07:27 Deploying the first temporary pull request (preview) release
13:17 Deploying more pull request (preview) releases
18:33 Removing deployments from closed pull requests (PRs)
21:06 What did we learn?
21:38 Outro
Gist with all the commands: gist.github.com/808108069f709...
Argo CD: Applying GitOps Principles To Manage Production Environment In Kubernetes: • Argo CD - Applying Git...
DevOps Catalog, Patterns, And Blueprints: www.devopstoolkitseries.com/p...
Books and courses: www.devopstoolkitseries.com
Podcast: www.devopsparadox.com/
Live streams: / devopsparadox