-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #4004 from shaedrich/gitops
Add topic "gitops"
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
display_name: GitOps | ||
short_description: GitOps is an operational framework that takes DevOps best practices and applies them to infrastructure automation. | ||
topic: gitops | ||
related: devops, winops, git, gitflow, devsecops, infrastructure-automation, infrastructure-as-code, containerization, monitoring, observability | ||
wikipedia_url: https://en.wikipedia.org/wiki/gitops | ||
--- | ||
**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. GitOps uses Git repositories as a single source of truth to deliver infrastructure as code. | ||
|
||
# GitOps delivers: | ||
* A standard workflow for application development | ||
* Increased security for setting application requirements upfront | ||
* Improved reliability with visibility and version control through Git | ||
* Consistency across any cluster, any cloud, and any on-premise environment | ||
|
||
# Key components of a GitOps workflow | ||
|
||
There are four key components to a GitOps workflow, a Git repository, a continuous delivery (CD) pipeline, an application deployment tool, and a monitoring system. | ||
* The Git repository is the source of truth for the application configuration and code. | ||
* The CD pipeline is responsible for building, testing, and deploying the application. | ||
* The deployment tool is used to manage the application resources in the target environment. | ||
* The monitoring system tracks the application performance and provides feedback to the development team. | ||
|
||
|