Flux deploy with access only to Registry1
Working with BigBang and deploying Flux with Release 1.52. My environment is whitelisted to registry1.dso.mil and repo1.dso.mil. However having some container issues that are reaching out to AWS S3 ( I believe ).
Currently attempting to deploy Flux using the BigBang Customer template and instructions here: https://repo1.dso.mil/big-bang/customers/template#configure-for-gitops
When getting to the part that deploys Flux for syncing, the pods are failing due to the following error:
Failed to pull image "registry1.dso.mil/ironbank/fluxcd/kustomize-controller:v0.32.0": rpc error: code = Unknown desc = failed to pull and unpack image "registry1.dso.mil/ironbank/fluxcd/kustomize-controller:v0.32.0": failed to copy: httpReadSeeker: failed open: failed to do request: Get "https://ib-prod-harbor-storage.s3.us-gov-west-1.amazonaws.com/docker/registry/v2/blobs/sha256/04/041161acd84a189a4c6342f7767431bb00f7ad0bd293d73a6b1a8b2870afaa13/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA3WVJMOQ753IFP4ES%2F20230206%2Fus-gov-west-1%2Fs3%2Faws4_request&X-Amz-Date=20230206T223512Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=11aaa37dd8daecf8a2c0f609014b892f372395bab31be1712d35eacf0efdaba0": EOF
Is the container reaching out to S3 to validate against the SHA that is supposedly hosted in the S3 Bucket? Is there a way to bypass this check or have it do the check another way?