Ctrl K
ComunidadGuías…
GITHUB · ANALIZADO

homelab

Kubernetes-based homelab with Talos OS, FluxCD, Helm and multiple applications including Calibre-web, Ollama, and a custom PostgreSQL cluster.

Ficha actualizada 22 sept 2026, 19:22 · upstream 22 sept 2026, 19:05 · release sin release detectada

Ver códigoProblemas y ayudaRepositorio ↗Sitio oficial
00

Qué es homelab

Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.

This repository contains the complete configuration of a Kubernetes-based homelab environment managed using GitOps principles with FluxCD. The project is designed for experimentation and learning, providing a stable, reproducible infrastructure that demonstrates how to deploy applications on bare-metal hardware through container orchestration.

The cluster runs on Talos OS, which provides zero-trust security, native Linux kernel support, and built-in observability out of the box. Applications are deployed using Helm charts with custom configurations tailored for this specific homelab environment. The infrastructure includes a dedicated server rack, multiple compute nodes, a firewall appliance, and distributed storage solutions.

Key components include a self-hosted LLM platform (Ollama), an ebook library manager (Calibre-web), network-wide ad-blocking (Pi-hole), and a custom PostgreSQL cluster managed through CloudNativePG. The system is orchestrated via FluxCD for declarative GitOps management, with automated dependency updates handled by Renovate.

CASOS DE USO
  • Run a self-hosted LLM platform locally without cloud dependencies
  • Deploy a complete web application stack on bare-metal hardware
  • Manage multiple microservices using Kubernetes and Helm charts
  • Implement network-level security with OPNsense firewall
  • Automate infrastructure updates through GitOps pipelines
  • Provide distributed storage for persistent data volumes
PUNTOS DESTACADOS
  • Zero-trust architecture via Talos OS kernel, eliminating the need for traditional host-based firewalls
  • GitOps workflow with FluxCD enables declarative and reproducible deployments from Git repositories
  • Custom Helm chart 'one-chart' provides a flexible abstraction layer for deploying non-standard applications
  • Distributed block storage via Longhorn ensures data durability across multiple nodes in the cluster
  • Pi-hole integrated as both DNS resolver and network-level ad blocker, reducing bandwidth usage
  • CloudNativePG manages PostgreSQL clusters with native Kubernetes support and automatic upgrades
PRECAUCIONES
  • No GPU acceleration is available on any node, limiting AI/ML workloads that require dedicated hardware
  • The custom server rack requires manual physical installation and maintenance of components
  • Longhorn storage does not provide raw block device access for direct I/O operations
  • External DNS propagation through Pi-hole may introduce slight latency in name resolution
  • No built-in backup mechanism beyond NFS-based Longhorn backups, requiring external tools like rsync
01

Perfil de infraestructura

Estimación inicial derivada del repositorio y de los servicios detectados.

CPU4 vCPUrecomendación inicial
MEMORIA8 GBRAM estimada
DISCO20 GBalmacenamiento base
COMPLEJIDADhighnivel de operación
02

Despliegue detectado

Qué señales reales de instalación hemos encontrado.

Despliegue manual

To deploy this homelab, first install Talos OS on the server rack and configure your Kubernetes cluster using the provided Helm chart. Deploy FluxCD as a GitOps operator to manage all resources declaratively from a Git repository. Use the 'one-chart' Helm release for applications that lack dedicated charts, such as Calibre-web or Ollama. For PostgreSQL, use the CloudNativePG chart with appropriate resource requests and limits. Enable longhorn storage via the provided manifest files. Configure OPNsense on the firewall appliance to allow traffic only from the Kubernetes cluster's internal network (10.244.0.0/24). Monitor health using Gatus or Headlamp, and regularly review FluxCD pipelines for dependency updates.

—Dockerfile
—Compose
—One-click
03

Stack y dependencias

Componentes inferidos a partir de manifests, configuración y documentación.

FRAMEWORKS
Node.js
SERVICIOS
PostgreSQL
BASES DE DATOS
PostgreSQL
PUERTOS
No detectados
05

Puede sustituir a

Relaciones detectadas por el análisis del repositorio y su categoría.

06

Experiencia real de la comunidad

Ayuda a contrastar la estimación automática con instalaciones reales.

Todavía no hay datos comunitarios para este proyecto.