Big Bang package downloads targeting East Australian Azure data centers time out
Summary
we're now seeing similar timeout issues to #1389 (closed) for P1 deployments targeting Azure AKS cluster nodes running within the Australian East data centers:
Failed to pull image "registry1.dso.mil/ironbank/fluxcd/helm-controller:v0.22.2": rpc error: code = Unknown desc = failed to pull and unpack image "registry1.dso.mil/ironbank/fluxcd/helm-controller:v0.22.2": failed to resolve reference "registry1.dso.mil/ironbank/fluxcd/helm-controller:v0.22.2": failed to do request: Head "https://registry1.dso.mil/v2/ironbank/fluxcd/helm-controller/manifests/v0.22.2": dial tcp 15.205.173.153:443: i/o timeout
This issue is preventing Azure customers from deploying Big Bang using the AUS DCs.
- initial issue raised with BigBang initiative 1416
Steps to reproduce
Pull any image from ironbank in an AKS resource in any Australian Azure DC
What is the current bug behavior?
timeout
What is the expected correct behavior?
Being able to pull images
Relevant logs and/or screenshots
Failed to pull image "registry1.dso.mil/ironbank/fluxcd/helm-controller:v0.22.2": rpc error: code = Unknown desc = failed to pull and unpack image "registry1.dso.mil/ironbank/fluxcd/helm-controller:v0.22.2": failed to resolve reference "registry1.dso.mil/ironbank/fluxcd/helm-controller:v0.22.2": failed to do request: Head "https://registry1.dso.mil/v2/ironbank/fluxcd/helm-controller/manifests/v0.22.2": dial tcp 15.205.173.153:443: i/o timeout
Possible fixes
Whitelist IPs assigned to Azure Australia regions
Notes
- This comes from an initial issue raised with BigBang initiative link