- Notifications
You must be signed in to change notification settings - Fork9
GitOps principles to define kubernetes cluster state via code
License
wrmilling/k3s-gitops
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Using GitOps principals and workflow to manage a lightweightk3s cluster.
This repository utilizesFlux2 to implement GitOps principals and define the state of my cluster using code.
Setup for the individual nodes is now via NixOS and mynixos-configuration repository. Individual node names from the screenshot inoverview can be searched for under thehosts
directory of the aforementioned repo.
The current cluster consists of one (1) virtual master node, hosted on my TrueNAS Scale NAS, three (3) Minisforum UN100C mini-PCs, and one (1) BMax B4 Plus mini-PC. The mini-PCs double as both compute and ceph nodes.
Setup for Flux2, secrets, and the rest of the GitOps workflow can be found here under thesetup directory.
A huge thanks to the community at Home Operations viadiscord chat. Home Operations Logo image used with permission, check out the community for some awesome and helpful people.
About
GitOps principles to define kubernetes cluster state via code