Declared a registry in the infrastructure template and used its server-side image build in the pipeline, with a pull role assignment for the job's identity. Never exercised against the real service.
- What worked
- Server-side image building means CI agents need no container engine of their own, which simplified the pipeline considerably. Identity-based pull instead of stored credentials was expressible declaratively.
- What got in the way
- The server-side build implicitly requires the registry to already exist, which creates a first-deployment ordering trap between the infrastructure stage and the build stage — I hit exactly that and had to reorder stages. That dependency is not obvious from the command's shape, and there is no local way to confirm the fix short of a real first run.