filmov
tv
What is GitOps, Practical GitOps CI/CD With Terraform and AWS
Показать описание
What is GitOps & How it Works | Practical GitOps Demo with Terraform + AWS Infra + CI/CD With AWS CodePipeline + AWS CodeCommit (Git Source) + AWS CodeBuild (CI/CD)
Learn:
What is GitOps?
What is Infrastructure as Code?
How Infrastructure as Code Works?
How GitOps is Useful for Infrastructure as Code?
How does GitOps merge request Flow work?
Continuous Integration and Continuous Deployment (CI/CD) for GitOps
Benefits of GitOps
How to achieve GitOps goal via Terraform in AWS Infra
(Detailed Terraform code explanation and full end-to-end practical hands-on tutorial)
#gitops #devops #learnwithsandip
▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬
0:00 - Intro
0:09 - What is GitOps?
0:28 - What is Infrastructure as Code?
1:08 - What are the Benefits of Infrastructure as Code?
1:42 - How does infrastructure as Code Works?
2:17 - Why use GitOps for Infrastructure As Code?
2:47 - GitOps Merge Request Flow
3:22 - CI Pipeline
3:43 - CD Pipeline
4:07 - Push Based Deployment & Pull Based Deployment
4:47 - Benefits of GitOps
5:51 - Practical GitOps
6:00 - Terraform Source Code Explanation
9:45 - Terraform init, validate, plan and apply
15:09 - GitOps Merge Request Flow Demo
22:27 - Wrap up
GitOps is an operational framework that takes DevOps best practices used for application development such as version control, collaboration, compliance, and CI/CD, and applies them to infrastructure automation.
It is a way of implementing Continuous Deployment for cloud-native applications. It focuses on a developer-centric experience when operating infrastructure, by using tools developers are already familiar with, including Git and Continuous Deployment tools.
The core idea of GitOps is having a Git repository that always contains declarative descriptions of the infrastructure currently desired in the production environment and an automated process to make the production environment match the described state in the repository. If you want to deploy a new application or update an existing one, you only need to update the repository - the automated process handles everything else. It’s like having cruise control for managing your applications in production.
GitOps = IaC + MRs + CI/CD
Infrastructure as Code(IaC): GitOps uses a Git repository as the single source of truth for infrastructure definitions. Git is an open-source version control system that tracks code management changes, and a Git repository is a .git folder in a project that tracks all changes made to files in a project over time. Infrastructure as code (IaC) is the practice of keeping all infrastructure configurations stored as code. The actual desired state may or maybe not be stored as code (e.g., number of replicas or pods).
Merge Requests (MRs): GitOps uses merge requests (MRs) as the change mechanism for all infrastructure updates. The MR is where teams can collaborate via reviews and comments and where formal approvals take place. A merge commits to your main (or trunk) branch and serves as an audit log.
Continuous Integration & Continuous Deployment(CI/CD): GitOps automates infrastructure updates using a Git workflow with continuous integration and continuous delivery (CI/CD). When new code is merged, the CI/CD pipeline enacts the change in the environment. Any configuration drift, such as manual changes or errors, is overwritten by GitOps automation so the environment converges on the desired state defined in Git. GitLab uses CI/CD pipelines to manage and implement GitOps automation, but other forms of automation, such as definitions operators, can be used as well.
▬▬▬▬▬▬ Useful Links 🔗🚀 ▬▬▬▬▬▬
▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬
Join this channel to get access to perks:
Legal Notice:
AWS, GitLab, Jenkins, Terraform logos, etc are trademarks or registered trademarks of respective companies in the United States and/or other countries. These companies and other parties may also have trademark rights in other terms used herein. This video is not accredited, certified, affiliated with, nor endorsed by AWS, GitLab, Terraform, or HashiCorp, etc.
Learn:
What is GitOps?
What is Infrastructure as Code?
How Infrastructure as Code Works?
How GitOps is Useful for Infrastructure as Code?
How does GitOps merge request Flow work?
Continuous Integration and Continuous Deployment (CI/CD) for GitOps
Benefits of GitOps
How to achieve GitOps goal via Terraform in AWS Infra
(Detailed Terraform code explanation and full end-to-end practical hands-on tutorial)
#gitops #devops #learnwithsandip
▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬
0:00 - Intro
0:09 - What is GitOps?
0:28 - What is Infrastructure as Code?
1:08 - What are the Benefits of Infrastructure as Code?
1:42 - How does infrastructure as Code Works?
2:17 - Why use GitOps for Infrastructure As Code?
2:47 - GitOps Merge Request Flow
3:22 - CI Pipeline
3:43 - CD Pipeline
4:07 - Push Based Deployment & Pull Based Deployment
4:47 - Benefits of GitOps
5:51 - Practical GitOps
6:00 - Terraform Source Code Explanation
9:45 - Terraform init, validate, plan and apply
15:09 - GitOps Merge Request Flow Demo
22:27 - Wrap up
GitOps is an operational framework that takes DevOps best practices used for application development such as version control, collaboration, compliance, and CI/CD, and applies them to infrastructure automation.
It is a way of implementing Continuous Deployment for cloud-native applications. It focuses on a developer-centric experience when operating infrastructure, by using tools developers are already familiar with, including Git and Continuous Deployment tools.
The core idea of GitOps is having a Git repository that always contains declarative descriptions of the infrastructure currently desired in the production environment and an automated process to make the production environment match the described state in the repository. If you want to deploy a new application or update an existing one, you only need to update the repository - the automated process handles everything else. It’s like having cruise control for managing your applications in production.
GitOps = IaC + MRs + CI/CD
Infrastructure as Code(IaC): GitOps uses a Git repository as the single source of truth for infrastructure definitions. Git is an open-source version control system that tracks code management changes, and a Git repository is a .git folder in a project that tracks all changes made to files in a project over time. Infrastructure as code (IaC) is the practice of keeping all infrastructure configurations stored as code. The actual desired state may or maybe not be stored as code (e.g., number of replicas or pods).
Merge Requests (MRs): GitOps uses merge requests (MRs) as the change mechanism for all infrastructure updates. The MR is where teams can collaborate via reviews and comments and where formal approvals take place. A merge commits to your main (or trunk) branch and serves as an audit log.
Continuous Integration & Continuous Deployment(CI/CD): GitOps automates infrastructure updates using a Git workflow with continuous integration and continuous delivery (CI/CD). When new code is merged, the CI/CD pipeline enacts the change in the environment. Any configuration drift, such as manual changes or errors, is overwritten by GitOps automation so the environment converges on the desired state defined in Git. GitLab uses CI/CD pipelines to manage and implement GitOps automation, but other forms of automation, such as definitions operators, can be used as well.
▬▬▬▬▬▬ Useful Links 🔗🚀 ▬▬▬▬▬▬
▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬
Join this channel to get access to perks:
Legal Notice:
AWS, GitLab, Jenkins, Terraform logos, etc are trademarks or registered trademarks of respective companies in the United States and/or other countries. These companies and other parties may also have trademark rights in other terms used herein. This video is not accredited, certified, affiliated with, nor endorsed by AWS, GitLab, Terraform, or HashiCorp, etc.
Комментарии