Projects with this topic
-
My personal k8s homelab cluster
Updated -
My fully-automated DevOps homelab.
Updated -
My NixOS flake.
Updated -
-
-
Homelab Ansible Playbooks and Roles
Updated -
-
Command line utility to import HomeBank's files to Firefly III
Updated -
-
Personal NixOS flake for my laptop, desktop, homelab and Raspberry Pi.
Updated -
Public mirror of my homelab repository
Updated -
Media library cleanup automation for self-hosted homelabs — Plex/Jellyfin + Sonarr/Radarr/qBittorrent
Updated -
-
Homelab infrastructure as code - Proxmox, Docker (dockhost), Kubernetes (kubecluster), Bastion
Updated -
-
tf-modules — Reusable Terraform Modules
The building blocks of the homelab private cloud — composable, versioned, and consumed by tf-infra.
Reusable Terraform modules for provisioning homelab infrastructure. Each module is independently versioned via semver git tags and sourced by tf-infra over SSH.
Modules network: NAT network with DHCP and local DNS via libvirt UsageModules are referenced in tf-infra via git SSH source:
module "network" { source = "git::ssh://git@gitlab.com/yggdrasil13/hnoss/tf-modules.git//modules/network?ref=v0.1.0" } Tech Stack IaC: Terraform (managed via tfenv) Provider: libvirt Versioning: Semver git tags (v0.1.0, v0.2.0, ...)Updated -
tf-infra — Live Terraform Infrastructure
Provisions and manages the homelab private cloud using reusable modules from tf-modules.
Live Terraform configurations that compose modules from tf-modules to provision actual infrastructure. Each environment is an independent root module with its own state.
Environments production: NAT network 10.0.100.0/24, DHCP, local DNS via libvirt staging: NAT network 10.0.101.0/24, separate domain (staging.homelab.local) What's in here environments/production/: Production root module — network layer, state, tfvars environments/staging/: Staging root module — mirrors production with isolated state CI/CD: terraform fmt + terraform validate for all environments, AI code review, semver auto-tagging Tech Stack IaC: Terraform (managed via tfenv) Provider: libvirt Modules: Sourced from yggdrasil13/hnoss/tf-modules via git SSH + semver tagUpdated -
k8s-config — Kubernetes Cluster Configuration
GitOps repository for the homelab k3s cluster — everything the cluster runs is defined here.
Manages all Kubernetes workloads and cluster-level configuration for a bare-metal k3s cluster with NVIDIA GPU passthrough. Deployed via Flux CD with Kustomize overlays for production and staging environments.
What's in here Flux GitOps: Kustomization CRDs in clusters/production/ and clusters/staging/ Base layer: Namespaces, ingress, NVIDIA device plugin, Weave GitOps dashboard Apps layer: Ollama (LLM serving), Open WebUI, ComfyUI (image generation), GitLab runner CI/CD: Schema validation (kubeconform), kustomize build checks, Flux CRD validation, AI code review Tech Stack Orchestration: k3s (bare-metal) GitOps: Flux CD v2 Config management: Kustomize GPU: NVIDIA passthrough with runtimeClassName: nvidiaUpdated -
Hofund — AI Code Review Bot
Named after Heimdall's sword — the gatekeeper that nothing passes without scrutiny.
Hofund is a GitLab-integrated bot that automatically reviews merge requests before they are merged. It uses a locally-hosted LLM (via Ollama) to analyse diffs and post structured feedback as MR comments.
Features (planned) Triggered on MR open and update via GitLab CI pipeline Analyses the diff and posts a structured review comment Flags hardcoded secrets, credentials, and environment variables Detects common anti-patterns and code smells Summarises what changed and why it may be risky Tech Stack Language: Go Model: Local LLM via Ollama (no external API calls) Integration: GitLab CI + GitLab REST API Security scanning: Snyk, SonarQubeUpdated -
An opinionated, single-host appliance for running a secure, self-hosted media stack on openSUSE MicroOS.
Updated