GitOps topic
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.
plural
Deploy open source software on Kubernetes in record time. 🚀
helm-operator-get-started
Managing Helm releases with Flux Helm Operator
eunomia
A GitOps Operator for Kubernetes
flux-get-started
Flux v1: Getting started with Flux and the Helm Operator
kapp-controller
Continuous delivery and package management for Kubernetes.
AzOps
AzOps is a PowerShell module which deploys (Push) ARM Resource Templates & Bicep files at all Azure scope levels and exports (Pull) ARM resource hierarchy.
bedrock
Automation for Production Kubernetes Clusters with a GitOps Workflow
tofu-controller
A GitOps OpenTofu and Terraform controller for Flux
vscode-gitops-tools
GitOps Visual Studio Code Extension