In this video I’m setting up Harbor in my Kubernetes homelab and using it as a proxy cache in front of Docker Hub. The whole point is simple: stop getting wrecked by Docker Hub pull limits (especially with the April 1st, 2025 changes—10 pulls/hour unauthenticated and 100 pulls/hour on a free authenticated account) and speed up image pulls by keeping the stuff you use all the time inside your own network. If you’re running a bunch of CI/CD pipelines or you’re like me and you’re constantly spinning up random self-hosted apps and test containers, you can hit those limits way faster than you’d think. I walk through installing Harbor with Helm, setting the external URL, deploying it into a dedicated namespace, and then wiring up ingress correctly (this part matters). Harbor splits things across microservices, so I show the Traefik routing rules that need to send specific paths (like /api and /v2) to “core” instead of only forwarding everything to the portal—otherwise login gets weird even with the right credentials. After that, I create a Docker Hub registry entry in Harbor, create a public proxy-cache project, and demo pulling an image through Harbor so it caches locally. Bonus: Harbor’s built-in vulnerability scanning is a really nice extra so you can see what you’re actually pulling into your lab.