Harbor / Nexus / Artifactory — Prerequisites
What to Know Before Starting Harbor
Harbor is a registry — the prerequisites are almost entirely about understanding container images and Docker workflows, since that's what Harbor stores, scans, and replicates.
Required (Must Have)
1. Docker/Container Image Basics
You need to understand what an image tag is, what pushing/pulling actually does, and basic Docker registry authentication (docker login) — Harbor is a registry you interact with using these exact same commands, just pointed at a different host.
2. Basic Kubernetes Awareness (For the Deployment Path)
Harbor itself is typically deployed via Helm onto Kubernetes for production use — you don't need deep K8s expertise, just enough to deploy and inspect a Helm-installed application.
3. Basic Understanding of Vulnerability Scanning Concepts
Nice to Have (Speeds Up Learning)
Cloud Registry Experience (ECR/ACR/GCR)
Overview's own framing is the fastest on-ramp: if you've used a cloud-native registry before, Harbor's Projects (namespaces with their own RBAC/scanning/retention) map to a familiar mental model — you're learning what Harbor adds on top, not registries from scratch.
Terraform Basics (Optional)
Advanced's API-automation-at-scale material uses Harbor's Terraform provider for project provisioning — prior Terraform exposure (this site's Terraform section) makes that module immediately familiar syntax.
CI/CD Pipeline Experience
Webhooks (Intermediate) are most useful in the context of a CI pipeline reacting to a scan-complete event — prior exposure to any CI/CD tool (GitLab CI, GitHub Actions, Jenkins) makes that pattern click faster.
What You Do NOT Need
Time Estimate
If you have the prerequisites above:
Start Here
Go to the Installation section to deploy Harbor, then proceed to Fundamentals.

