GitOps: Difference between revisions
No edit summary |
|||
| Line 6: | Line 6: | ||
* [[Git]] | * [[Git]] | ||
=Overview= | =Overview= | ||
GitOps is a way of implementing [[ | GitOps is a way of implementing [[Continuous_Delivery#Overview|Continuous Delivery]] 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 Delivery 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. | ||
=Organizatorium= | =Organizatorium= | ||
<font color=darkkhaki> | <font color=darkkhaki> | ||
Revision as of 01:54, 1 January 2022
External
Internal
Overview
GitOps is a way of implementing Continuous Delivery 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 Delivery 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.
Organizatorium
TO PROCESS: