The GoProxy egress-check init container only handled x86_64 and aarch64. On the xu4 node, uname -m is armv7l, so the init container exited with unsupported architecture: armv7l and the Deployment stayed in CrashLoopBackOff.
Fix
select the upstream GoProxy v15.3 proxy-linux-arm-v7.tar.gz asset for armv7l;
verify it with its pinned SHA-256 checksum;
document ARMv7 support.
This PR is limited to the GoProxy workload and does not change the registry-DNS or connectivity-tester PRs.
Validation: git diff --check, architecture-to-asset mapping for x86_64, aarch64, and armv7l, and SHA-256 verification of the downloaded upstream ARMv7 release asset.
## Problem
The GoProxy egress-check init container only handled `x86_64` and `aarch64`. On the `xu4` node, `uname -m` is `armv7l`, so the init container exited with `unsupported architecture: armv7l` and the Deployment stayed in CrashLoopBackOff.
## Fix
- select the upstream GoProxy v15.3 `proxy-linux-arm-v7.tar.gz` asset for `armv7l`;
- verify it with its pinned SHA-256 checksum;
- document ARMv7 support.
This PR is limited to the GoProxy workload and does not change the registry-DNS or connectivity-tester PRs.
Validation: `git diff --check`, architecture-to-asset mapping for `x86_64`, `aarch64`, and `armv7l`, and SHA-256 verification of the downloaded upstream ARMv7 release asset.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The GoProxy egress-check init container only handled
x86_64andaarch64. On thexu4node,uname -misarmv7l, so the init container exited withunsupported architecture: armv7land the Deployment stayed in CrashLoopBackOff.Fix
proxy-linux-arm-v7.tar.gzasset forarmv7l;This PR is limited to the GoProxy workload and does not change the registry-DNS or connectivity-tester PRs.
Validation:
git diff --check, architecture-to-asset mapping forx86_64,aarch64, andarmv7l, and SHA-256 verification of the downloaded upstream ARMv7 release asset.