In this homelab Kubernetes streak video, I walk through getting GitLab running on Kubernetes the easy way: the official GitLab Helm chart. The big win here is that the runner setup is basically baked in, so you’re not off building a separate runner stack from scratch. Once you get past the initial “lots of moving parts” phase, it’s honestly amazing—especially for a homelab where you still want something that feels close to real-world CI/CD. I start with the stuff that will bite you if you skip it: DNS. The chart expects a handful of default hostnames (gitlab, kas, minio, and registry) under your domain, so I show what those should look like and why they matter. Then I go into the values.yaml tweaks: setting the base domain correctly (don’t do gitlab.gitlab… I made that mistake), using Traefik instead of the bundled NGINX ingress, and wiring up TLS with a self-signed cert from my step-ca setup. The part that took me the longest was making the runner trust the self-signed cert—once you add the cert secret to the runner config, it registers cleanly and jobs stop failing. I also hit storage limits during install (Longhorn volumes), fix it, and verify everything is up—including grabbing the initial root password and confirming the runner is online.