K3s cluster driven by Flux
-
Updated
Nov 11, 2025 - YAML
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.
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.
K3s cluster driven by Flux
GitOps repository of my Kubernetes homelab
My home kubernetes GitOps repository.
IaC for my HomeLab kubernetes cluster resources with Flux
suffering as a service
My GitOps-managed home Kubernetes cluster
HomeOps driven by Kubernetes and GitOps using Flux
Another Kubernetes repo — because one more won’t hurt.
My home or for-home infrastructure written as code, adhering to GitOps practices
My home operations repository using k8s/gitops
A mono repository for my home infrastructure and Kubernetes cluster which adheres to Infrastructure as Code (IaC) and GitOps practices where possible
Kubernetes cluster with Flux and Renovate
Kubernetes cluster deployed on Proxmox VE VMs with Talos Linux. Managed with Flux, Renovate and GitHub Actions
Wife tolerated HomeOps driven by Kubernetes, and Gitops via Flux.
The source of truth for my home cluster to reconcile from following GitOps where possible.
GitOps-driven Infrastructure as Code for my homelab
GitOps Homelab Environment
Wife approved HomeOps driven by Kubernetes and GitOps using Flux
A mono repository for my home infra and Kubernetes cluster adhering to Infrastructure as Code (IaC) and GitOps practices