[P1BIGROCKS-1705](https://jira.il2.dso.mil/browse/P1BIGROCKS-1705) Enable IB to use BB pipelines to functionally test new images. Just spent some time doing this so wanted to walk through the workflow as it currently exists: 1) Push new git commit to Iron Bank Repo (as part of an MR into development e.g. https://repo1.dso.mil/dsop/cluster-auditor/opa-collector/-/merge_requests/12) 2) Wait for pipeline to start and build stage to run: https://repo1.dso.mil/dsop/cluster-auditor/opa-collector/-/jobs/2571133 3) Download the artifact from the build 4) Untar it and run ```bash ❯ docker load -i ci-artifacts\ 5/build/opa-collector-208333.tar c7c2dd85c76a: Loading layer [==================================================>] 62.54MB/62.54MB Loaded image ID: sha256:d751122ec8ed92aeb2fc966982f667f164bdc579fc7ef34665482803a246ef92 ``` 5) Get the sha from the output to use in the tagging of the image: ```bash docker tag d751122ec8ed registry.dso.mil/platform-one/big-bang/apps/core/cluster-auditor/opa-collector:0.3.2-ib-208333 ``` 6) Push it up to the repo for the BigBang Package: ``` ❯ docker push registry.dso.mil/platform-one/big-bang/apps/core/cluster-auditor/opa-collector:0.3.2-ib-208333 The push refers to repository [registry.dso.mil/platform-one/big-bang/apps/core/cluster-auditor/opa-collector] c7c2dd85c76a: Pushed 919b1d243692: Layer already exists 55141e108e1c: Layer already exists 4986f8b966ab: Layer already exists db85f4e94c21: Layer already exists 9624be4353eb: Layer already exists 72e7d306c279: Layer already exists 0.3.2-ib-208333: digest: sha256:b827a569011fb996d5a379d8c923ee17fda688b849cd6ffd36f12832982e23ba size: 1796 ``` 7) re-deploy BigBang with the new image: ```bash ❯ helm upgrade -i bigbang chart -n bigbang -f dev/credentials.yaml -f chart/ingress-certs.yaml --set clusterAuditor.values.image.tag=0.3.2-ib-208333 --create-namespace ``` 8) Check of bigbang comes up healthy