How I added kagent images to Harbor without widening the allowlist
To mirror kagent’s runtime images into Harbor, I needed a way to approve the whole bundle while keeping the existing image allowlist in force. I added a dedicated kagent scope so the workflow could select a reviewed set of images.
A dedicated scope for the kagent bundle
The workflow, policy, and publisher now recognize the same scope. A dedicated catalog lists the reviewed runtime images, and the publisher checks the complete bundle against that catalog. The onboarding docs show how to use the new scope. Future image additions can go through a catalog review.
What the commit covers
The commit extends the publisher tests for the new scope and manifest handling. It also updates the static checks. My next check would be to run the mirror workflow for kagent and confirm that the expected images are available in Harbor.
How I’d onboard the next runtime
I’d use the same approach on a platform team that mirrors dependencies into an internal registry. I’d give each runtime a named scope and a reviewable catalog, then test whether the publisher enforces it. That gives reviewers a concrete question to answer during onboarding: which images does this runtime need, and does the catalog cover them?