{"repo":"wrmilling/k3s-gitops","free":true,"listed":false,"github":"https://github.com/wrmilling/k3s-gitops","clone":"git clone https://github.com/wrmilling/k3s-gitops.git","description":"GitOps principles to define kubernetes cluster state via code","language":"Shell","stars":230,"topics":["k3s","kubernetes","gitops","flux2","flux","helm","cert-manager","renovate","k8s-at-home","rook"],"license":"Apache-2.0","category":"deployment-docker-iac","readme_excerpt":"k3s-gitops Using GitOps principals and workflow to manage a lightweight k3s cluster. :book:  Overview This repository utilizes Flux2 to implement GitOps principals and define the state of my cluster using code. :computer:  Infrastructure Setup for the individual nodes is now via NixOS and my nixos-configuration repository. Individual node names from the screenshot in overview can be searched for under the hosts 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. :gear:  Setup Setup for Flux2, secrets, and the rest of the GitOps workflow can be found here under the setup directory. :wrench:  Namespaces cert-manager default development flux-system kube-system media monitoring rook-ceph social :handshake:  Credits + Community A huge thanks to the community at Home Operations via discord chat. Home Operations Logo image used with permission, check out the community for some awesome and helpful people.","default_branch":null,"files":null,"tree":[],"storefront":"/r/wrmilling","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/wrmilling/k3s-gitops/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}