Dan Manners' Homelab

Current status: BETA (but is highly stable)

This project aims to utilize industry-standard tooling and practices in order to both perform it's functions and act as a repository for people to reference for their own learning and work.

🔍 Features

• [x] Easy to replicate GitOps
• [x] Modularity; make it easy to add/remove components
• [x] Hybrid Multi-Cloud
• [x] External DNS updates
• [x] Automagic cert management
• [x] In-Cluster Container Registry
• [ ] Monitoring and alerting 🚧
• [ ] Automated Backups 🚧
• [x] ~~Cluster SSO through GitHub~~ - Removed when switching from K3s to Talos

💡 Current Tech Stack

Removed Tech Stack

Several items have previously been in my cluster, but have been removed over time for one reason or another. Those items can be foud below.

Services Hosted

Deprecated Services

The services listed below once existed in the cluster, but have since been removed for one reason or another

🔧 Hardware

Below is a list of the hardware (both physical and virtual) in use on this project

🖥 On-Prem Systems

Baremetal Talos Hosts

Cluster Boards

Additional Compute

Storage

Networking

Cloud Hosted Resources

Deployment Order of Operations

While this section is very much a Work-in-Progress, I'd like to provide some relevant information on core services that must be deployed and in which order.

1. Talos Linux
2. Cilium CNI
3. MetalLB
4. Cert-Manager
5. External-DNS
6. Traefik
7. ArgoCD - Part One
8. ArgoCD - Part Two

Identifying Problems, Troubleshooting Steps, and more

Below are a few things that may be beneficial to you when troubleshooting or getting things up and operational

Traffic is not getting from the edge (cloud) nodes to the on-prem cluster networking

You can validate that your remote traffic is or isn't making it on site by using dig inside of the netshoot container

kubectl run temp-troubleshooting \
  --rm -it -n default \
  --overrides='{"apiVersion":"v1","spec":{"nodeSelector":{"kubernetes.io/hostname":"talos-aws-grav01"}}}' \
  --pod-running-timeout 3m \
  --image=docker.io/nicolaka/netshoot:latest \
  --command -- /bin/bash

Then, you can validate that you can reach CoreDNS or another pod/service IP from your remote node.

If you can prove it is not working, you may want to restart all of Cilium:

kubectl rollout restart -n kube-system daemonset cilium

To-Do Items

• Ensure that ALL services are tagged for the appropriate hardware (arm64 or amd64) to ensure runtime success
  • Alternatively, ensure that all containers are built for multi-architecture.
• Ensure that ALL application and service subdirectories have READMEs explaining what they're doing and what someone else may need to modify for their own environment

Gratitude and Thanks

This README redesign was inspired by several other homelab repos, individuals, and communities.

Individuals

• zimmertr/TKS
• onedr0p/home-ops
• khuedoan/homelab

Communities

The DevOps Lounge

K8s-at-Home

Without the inspiration and help of these individuals and communities, I don't think my own project would be nearly as far. Make sure to check out their projects as well!