DevOps & Delivery · Images
Operate a registry that fits platform engineering: dashboard KPIs for projects and repositories (public vs private), storage totals, component health, vulnerability summaries with scanning signals, and recent activity for audits. Wire Cloud Admin to your Harbor v2.0 API for pull/push and proxy behavior—then tune connection, system configuration, logs, and administration without switching consoles.
Screenshots from the live product. Each note explains what you are looking at and when you would open this screen.
Your starting point for container registry: KPI cards and charts summarize fleet health, including harbor registry dashboard and security summary. Spot drift early, then drill into the tab that explains the root cause.
Click the screenshot to open full size, zoom, and pan.
Container registry projects list. This is the same interface your team uses in production.
Click the screenshot to open full size, zoom, and pan.
Registry system configuration. This is the same interface your team uses in production.
Click the screenshot to open full size, zoom, and pan.
Create registry user modal. This is the same interface your team uses in production.
Click the screenshot to open full size, zoom, and pan.
When storage, CVE posture, and audit trails share one plane with GitOps and Kubernetes, supply-chain conversations stay factual.
Project counts and public vs private splits keep accidental exposure visible.
Validate Harbor API connectivity before scans and proxies silently fail.
Quotas, read-only modes, and notifications land where admins already operate.
Run Container Registry from Cloud Admin alongside GitOps and Kubernetes workflows.
Get a demo