ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Grant Azure Container Registry pull access with the correct role mode, select the workload identity, and verify an immutable image without shared registry passwords.
Integration Boundary A Harbor project configured with a replication rule targeting an external Docker-compatible registry copies images and OCI artifacts on schedule or on demand. The replication path is additive by design: new tags and manifests appear at the destination, but the behavior when a tag or manifest is removed from the source project is not guar
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
Podman utilizes the standard Docker configuration format and external credential helpers to manage registry authentication. In rootless environments, this ensures least-privilege access by isolating credentials within the user's namespace and delegating secure storage to the helper. Currently, Podman does not maintain local metadata regarding the expiration
podman