Hey everyone! I'm a graduating student working on my capstone project, which involves creating a GitLab CI pipeline to provide a secure environment for students to practice Kubernetes—like creating pods, images, and managing pulls and pushes. I'm looking to implement Harbor as my private container registry, but I'm running into issues with harbor-cli since there's no official documentation for it. I want to set it up so each user has their own namespace in Kubernetes along with a secret for accessing the private registry. Additionally, I need to create users and assign RBAC permissions. If anyone has experience with this or can point me to a guide or example, I'd really appreciate it!
5 Answers
I’m curious why you prefer using Harbor over GitLab’s built-in image registry? What benefits do you anticipate from Harbor for your project?
If you decide to go ahead with Harbor, I'd recommend using the standard Helm charts—they're usually great to get you started, though you'll want to tweak the ingress settings.
Quay.io is another option you might want to consider as an image registry for your project.
Why the downvotes? It’s just another option. Anyway, I'm sticking with Harbor for now.
GitLab actually has its own built-in image repository you can utilize for storing your images. You might find that using Harbor just adds unnecessary complexity to the setup.
I get that, but my plan is to simulate a real company environment, so having a separate registry like Harbor might provide more benefits. Plus, I'd like to explore other tools, not just Docker Hub.
Harbor can be great for your needs, but user automation may get a bit complicated. Instead of using harbor-cli, I suggest tapping into the Harbor API directly for setting up users and projects.
What do you mean by ‘tricky’ in terms of user automation?
I'm planning to install Harbor on a separate VM, so I don’t think I’ll need Helm for that. The goal is to download the CLI module and handle the registry from the terminal since my main focus is on writing scripts.