[P1BIGROCKS-2658](https://jira.il2.dso.mil/browse/P1BIGROCKS-2658) Currently, Big Bang does not utilize a ```supported``` packaging tool for dependencies needed in an air gap environment. Additionally, we do not test that all required dependencies are part of the bundle. For each BB release, we should provide CI/CD tests for an opinionated / simulated air gap deployment to improve customer experience and instill confidence (via tests) by using a supported packaging tool / process that customers can enable customers for their Big Bang workflows and external dependencies. Initial thoughts on how to achieve this are: - [x] build a simulated airgap environment in AWS (internet disconnected / isolated VPC) - [x] utilize Zarf in an internet connected CI/CD stage to package up artifacts - [x] utilize Zarf to deploy k8s / Big Bang in an Air-Gap VPC - [x] validate all required artifacts are present and functional in the "airgap" by deploying BB and conducting E2E tests - [x] Add CI/CD Air-Gap testing to BB release process (tested per release) ### Out-of-Scope - underlying infra of choice - K8s distro of choice - any non-BB related bits that customers need to move into the void