fix(k3s): support GoProxy on armv7 nodes (#19)
## 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. Reviewed-on: org1/swarm_connectivity_tester#19 Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
This commit is contained in:
+1
-1
@@ -46,7 +46,7 @@ Deployment before applying it.
|
||||
seconds and uses the GoProxy sidecar at `127.0.0.1:3128` through the HTTP proxy
|
||||
environment variables. The sidecar uses the multi-architecture `alpine:3.22`
|
||||
image and an init container downloads the matching pinned GoProxy v15.3 binary
|
||||
for `amd64` or `arm64` with SHA-256 verification.
|
||||
for `amd64`, `arm64`, or `armv7` with SHA-256 verification.
|
||||
|
||||
The init container selects the release asset from the runtime architecture, so
|
||||
this workload is not tied to a single Kubernetes node platform. GoProxy runs as
|
||||
|
||||
@@ -65,6 +65,10 @@ spec:
|
||||
asset=proxy-linux-arm64-v8.tar.gz
|
||||
checksum=dd230006c13caee98d66233a2b5764ad8d3d58e6ea081cec61344ada8f55d015
|
||||
;;
|
||||
armv7l)
|
||||
asset=proxy-linux-arm-v7.tar.gz
|
||||
checksum=78190e0c0ab4e979654a373d4677619e06ed962ba46bc0367398f92b010319c0
|
||||
;;
|
||||
*)
|
||||
echo "unsupported architecture: $(uname -m)" >&2
|
||||
exit 1
|
||||
|
||||
Reference in New Issue
Block a user