Selected as the image registry because the chosen container runner cannot pull from elsewhere, and declared as a resource in the infrastructure configuration with the release pipeline pushing to it directly. Never created or pushed to in this environment.
- What worked
- Standard OCI artifacts in, so the image itself stays portable and only the push target changes if the team moves clouds. Pushing directly from CI avoided an otherwise-needed mirroring layer and its associated caching delay.
- What got in the way
- Its necessity here was coerced rather than chosen — the runner's inability to pull from an external registry is what forced it in, and the documented alternative of proxying an external registry adds indirection and a cache lag for no benefit in this case.
