Service Mesh on IBM s390x platform, how to enable?
summary
Envoy and OpenShift Service Mesh build and run on IBM s390x after specific engineering changes: a compatibility layer for BoringSSL maps BoringSSL calls to OpenSSL, the build toolchain switches from LLVM/clang to ld.gold with assembler workarounds, and dependencies like LuaJIT/luajit2 and quiche are patched for big‑endian byte order. WASM module serialization and runtimes are fixed so WASM and LUA extensions supported, tests still fail until asm/emscripten support is added, and ongoing maintenance is required.
AI-written summary · about
chapters (9)
- 0:00Service mesh on s390x intro
- 1:46Service mesh architecture & Envoy
- 4:17s390x challenges for Envoy
- 6:27OpenSSL layer for s390x
- 8:15Build toolchain for s390x
- 9:00Envoy dependency changes
- 10:48WebAssembly on s390x
- 13:24Feature parity & future
- 14:30Maintenance & closing
related talks
11mWelcome & Opening Remarks
30mService Mesh Is Still Hard. The Things we all Did Wrong & Tales of Woe
38mAsk Me Anything About Service Mesh
26mService Mesh Failure Stories at Scale
43mService Mesh and the future of networking
30mMultiplayer Istio: Collaborative WASM Plugins with Intel and Layer5
56mService Meshes - Powering the next wave of microservice architectures
35mNavigating the Service Mesh Ecosystem