Warning
Known Issue: the conformance suite in this release pins the v1.6.0 EPP image
conformance/resources/base.yaml at v1.6.1 still pins the EPP image to
registry.k8s.io/gateway-api-inference-extension/lwepp:v1.6.0. The release
tooling silently failed to rewrite it for a patch release (see #3054), so the v1.6.1 conformance suite deploys
the v1.6.0 EPP — the one without the fixes listed below.
Not affected: the released EPP image itself — lwepp:v1.6.1 is built and
promoted correctly — along with the CRDs and the root Go module. Only the
conformance manifest is wrong.
Workaround: override the EPP image to …/lwepp:v1.6.1 in your conformance
run, or wait for v1.6.2: #3052
Release Highlights
Gateway API Inference Extension v1.6.1 is a patch release addressing key bugs in Lightweight EPP (lwepp) stream handling and multi-architecture container images:
- LWEPP Full Duplex Body Responses (#3028): Ensure body responses in
FULL_DUPLEX_STREAMEDmode carry proper BodyMutation streamed responses, preventing gateway stream drops. - LWEPP ext_proc Stream Ordering (#3033): Answer request headers before request body in ext_proc gRPC streams. Resolves spurious response errors and HTTP 500 status codes when Envoy operates in
FULL_DUPLEX_STREAMEDmode with chunked request bodies. - Multi-Arch Docker Buildx Architecture Fix (#3032): Respect Docker buildx
TARGETARCHinstead of hardcodingGOARCH=amd64inlwepp.Dockerfile, fixingexec format errorcrashes onlinux/arm64hosts.
What's Changed
- Fix LWEPP full duplex body responses by @howardjohn in #3028
- fix(lwepp): respect buildx TARGETARCH instead of hardcoding GOARCH=amd64 by @tamil-deds in #3032
- fix(lwepp): answer request headers before request body by @bartoszmajsak in #3033
New Contributors
- @tamil-deds made their first contribution in #3032
- @bartoszmajsak made their first contribution in #3033
Full Changelog: v1.6.0...v1.6.1