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.
apisix-control-plane
The Control-Plane for APISIX
korthweb
Orthanc on Kubernetes
kochhaus-home
Experimental homelab configuration for running things on kubernetes
commodore
Commodore provides opinionated tenant-aware management of Kapitan inventories and templates. Commodore uses Kapitan for the heavy lifting of rendering templates and resolving a hierachical configurati...
actions
GitOps actions
instruqt
Repository for the Red Hat and OpenShift Developers Learning Portal, powered by Instruqt.
home-ops
Wife approved HomeOps driven by Kubernetes, and Gitops via Flux.
kube-template
GitOps repository template
home-cluster
My home Kubernetes (k3s) cluster managed by GitOps (Flux2)
waffle-world
[K8S] everything in wafflestudio-cluster