A city Wi-Fi captive portal image contains only amd64 binaries, but…

Question

A city Wi-Fi captive portal image contains only amd64 binaries, but several worker nodes are arm64. What should the team do?

Accepted Answer

Publish and pull a multi-arch image (or matching arch tag) that fits the node architecture — Handing an amd64 binary to an arm64 node is like shipping a vinyl record player a cassette—wrong format. Build multi-arch manifests or arch-specific tags so each node pulls an image it can actually run.

Answer

Schedule the amd64-only image onto arm64 nodes and rely on qemu emulation always being present

Answer

Delete the arm64 nodes so every application can ignore architecture

Answer

Set imagePullPolicy to Never to skip architecture checks during kubelet image verification

A city Wi-Fi captive portal image contains only amd64 binaries, but several worker nodes are arm64. What should the team do?

Short Explanation

Full Explanation