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.
git-proxy
Deploy custom push protections and policies on top of Git
gitops-linkerd
Progressive Delivery workshop with Linkerd, Flagger and Flux
homelab
Small and energy-efficient self-hosting infrastructure.
flux2-gitops
Multi-cluster GitOps repository with Flux2, SOPS & Renovate
homelab
IaC for my homelab & personal cloud.
home-ops
Repository for home infrastructure and monorepo for kubernetes cluster
gitops-zombies
Identify kubernetes resources which are not managed by GitOps
fabrikate
Making GitOps with Kubernetes easier one component at a time
flux-aio
Flux All-In-One distribution made with Timoni