Kubernetes

During my last homelabbing session, I ran into a problem that initially felt annoying but eventually turned into a surprisingly elegant solution—one worth sharing. The Problem I run a private server in my apartment hosting various homelab services. By design, this server is not directly accessible from the public internet. I want to keep my internal services private and under my control. For remote access while traveling, I rely on Tailscale. This allows me to securely access services like paperless-ngx from my phone or laptop without exposing anything publicly. So far, this setup has worked flawlessly. ...

Introduction Nextcloud is a self-hosted collaboration platform that provides file synchronization and sharing, calendars, contacts, and a growing ecosystem of apps. It offers strong data ownership guarantees while still covering many use cases typically handled by managed cloud services. So my goal is to replace Google Drive, Contacs and Calendar with a self-hosted nextcloud instance. In my homelab, I run a lightweight Kubernetes distribution based on k3s. To keep the deployment reproducible, maintainable, and aligned with cloud-native best practices, I decided to deploy Nextcloud using its Helm chart rather than relying on ad-hoc manifests or manual container setups. Helm allows me to describe the desired state declaratively, manage upgrades more safely, and keep configuration changes version-controlled. This is the first step to go to manage my K3S cluster using Argo CD. ...