search

wrmilling / k3s-gitops

GitOps principles to define kubernetes cluster state via code
Apache License 2.0
213 stars 8 forks source link
cert-manager flux flux2 gitops grafana helm k3s k8s-at-home kubernetes metallb nginx-ingress prometheus renovate rook sops velero

readme

k3s-gitops

Image used with permission from k8s-at-home

k3s GitHub Stars GitHub Last Commit Home Operations Discord

Using GitOps principals and workflow to manage a lightweight k3s cluster.

:book:  Overview

k3s Nodes

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

:handshake:  Credits + Community

A huge thanks to the community at Home Operations via awesome-home-kubernetes and the discord chat. Home Operations Logo image used with permission, check out the community for some awesome and helpful people.