My self-hosting infrastructure, fully automated (github.com)

Article summary

The article presents a fully automated homelab infrastructure, utilizing Infrastructure as Code and GitOps to automate provisioning, operating, and updating self-hosted services. The project is highly customizable and can be used as a framework to build a homelab. It features automated bare metal provisioning, Kubernetes installation and management, and automatic rolling upgrades for OS and Kubernetes. The infrastructure is designed to be secure and scalable, with features like automated certificate management and VPN access.

Main themes

• Homelab infrastructure
• Automation and scalability
• Security and privacy
• Self-hosting vs SaaS
• VPN and remote access
• Infrastructure as Code and GitOps
• Technical trade-offs and complexity management

What commenters say

• Tailscale is a useful tool for securely accessing a homelab from outside the home network, but it may have privacy and security concerns due to its use of coordination servers.
• Some users prefer Tailscale for its ease of use and NAT busting capabilities, while others prefer vanilla Wireguard for its simplicity and lack of dependencies.
• Self-hosted alternatives to Tailscale, such as Netmaker and HeadScale, offer more control and flexibility, but may require more technical expertise to set up and maintain.
• The use of client-side certificates can provide an additional layer of security for accessing web services, but can be inconvenient to manage.
• The complexity of the homelab infrastructure presented in the article is seen as both a learning opportunity and overkill by different commenters.
• The decision to self-host services rather than using SaaS products is driven by concerns about reliability, security, and control.
• The choice between using Tailscale and other VPN solutions, such as Wireguard, depends on individual needs and priorities, including ease of use, security, and performance.