ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #harbor
Integration boundary Harbor v2.x exposes two distinct pagination contracts: the project-scoped repository and artifact endpoints use page (1-based) and page_size (max 100), while the global search endpoint /api/v2.0/search uses limit and offset . A client that must both enumerate all repositories in a project and perform cross-project searches therefore need
Goal I am designing a replication strategy between two Harbor instances and need to decide whether a replication policy should use event-driven triggers or a cron schedule. The registry also runs garbage collection and vulnerability scans through the same jobservice, so the choice affects more than just replication latency. Constraints and uncertainty From t
Background When creating a Harbor project through the REST API, the public field is optional. In v1.x the default was true , while v2.0+ changed the default to false . However, the Helm chart and UI may still apply the legacy default in some minor releases, leading to inconsistent visibility. This ambiguity is critical because anonymous users can pull images
Goal We need to increase the number of tags retrieved per API call to reduce round‑trips for large repositories. The default page_per_page is 20, but Harbor 2.8+ allows up to 1000. Constraints & Uncertainty Maximum page_per_page is 1000, configurable via harbor.ui.tagPaginationLimit in harbor.yml , requiring a restart. Large requests (>500 tags) risk
Harbor exposes the Docker Registry HTTP API v2 resumable upload at /v2//blobs/uploads/. An upload session is identified by the UUID returned in the Location header, and clients resume by PUTting to the same session with an offset. The design goal is to allow safe retries of chunk uploads without creating duplicate writes to the underlying storage before laye
Harbor's garbage collection mechanism uses retention policies to automatically remove image tags that exceed configured age or frequency thresholds. This feature helps organizations enforce storage budgets and compliance mandates. However, the documented specifications do not describe how an active image pull session behaves when its target tag is marked for
Problem Context When an upstream registry updates a mutable tag, Harbor’s proxy cache may still serve a previously cached manifest. The Docker client then receives a 404 Not Found when pulling the new digest, indicating that the proxy cache has not yet been refreshed. Constraints & Uncertainty Proxy cache entries are governed by a configurable TTL, and H
A common production deployment pattern for Harbor involves transitioning from the default local filesystem to S3-compatible object storage to support high availability across multiple nodes. This shift changes how the registry handles image layers, as the registry component must provide the client with a redirect URL to the object storage bucket. When the ex
Harbor LDAP over TLS: Supplying Custom CA Certificates The goal is to allow Harbor’s LDAP authentication module to trust a self‑signed or internal CA‑signed LDAP server certificate without altering the host’s global trust store or disabling verification. Current Harbor releases (2.0‑2.12) rely on the Go LDAP library’s default certificate pool, and the extern