images.txt includes all the images need to run and test the package. The images referenced in images.txt are provided in the images.tar.gz file -- including bigbang-ci/gitlab-tester.
One can get access to the image by running the registry2 server and then configuring their docker runtime to point to that registry2 instance and then issuing a docker pull bigbang-ci/gitlab-tester:0.0.4
Hopefully this alleviates your issue, i will be closing the issue. Let me know if you still require assistance.
Hopefully, that makes sense @rmcdaniel.nextgen . I did verify the gitlab-tester:0.0.4 is provided in the images.tag.gz file--it just requires a bit of setup there to actually get the docker image.
This image isn't required to run gitlab--only needed for testing.
So, I think to answer your original question, all the images should be "available", but there might be a few like this that can not be pulled directly.
It looks like gitlab and velero both reference "test" images from registry1.dso.mil/bigbang-ci/gitlab-tester .
I'll reach out to IB to see if maybe we can do something similar like they did in #178 (closed) to allow pulls on those images.
after some more digging, I think we need to just remove the gitlab-tester reference from gitlab's Chart.yaml . This image isn't used anymore -- we actually use registry1.dso.mil/bigbang-ci/devops-tester:1.1.2 . registry1.dso.mil/bigbang-ci/devops-tester:1.1.2 isn't referenced in other packages' Chart.yaml. So, for consistency, I'd say we just remove it from gitlab's Chart.yaml too.
The thought is that we don't want to open up access to bigbang-ci, since these images are "internal", and not hardened for general use. End-users can rebuild the images from the packages' Dockerfile if they want them.
@rmcdaniel.nextgen this will fix the images.txt reference. If users want the test image, the recommendation will be to manually build it from the provided Dockerfile.