Is it possible to upload containers to the Balena registry without triggering a release and then refer to these containers at a later stage?
Our CI/CD system produces between 20 different containers for 50 different balena apps and that number will grow. Since we cannot deploy the same container to multiple apps without uploading them for every app during deployment we would like the CI system to pre-load the containers to the Balena repos so that we can refer to them later. This would also allow us to get around the fact that the Balena AWS repo endpoints are in the us-east region which creates significant latency at this scale.
Ideally, we would prefer if Balena could just pull images from our AWS ECR repo when we trigger a release but that does not seem to be possible. The
--release-secrets option for
balena deploy is just a simpler version of
docker pull ; docker push which does not help much.
Second best option would be if we would have a single repo in Balena to which we can upload images so that we can refer to them in later releases.