Skip to content

fix(gateway-api): support non-403 directResponse via EnvoyFilter#198

Merged
mrdntgrn merged 1 commit intomainfrom
010-gateway-direct-response
Apr 9, 2026
Merged

fix(gateway-api): support non-403 directResponse via EnvoyFilter#198
mrdntgrn merged 1 commit intomainfrom
010-gateway-direct-response

Conversation

@mrdntgrn
Copy link
Copy Markdown
Contributor

@mrdntgrn mrdntgrn commented Apr 8, 2026

Summary

  • add Istio EnvoyFilter rendering for httpRoutes[].rules[].directResponse when status is 200-599 (excluding 403), with default body ""
  • keep existing 403 behavior unchanged via AuthorizationPolicy and preserve precedence semantics
  • update chart docs/examples/spec artifacts and bump charts/gateway-api chart version to 0.1.5

Test plan

  • helm lint ./charts/gateway-api
  • helm template gateway-api ./charts/gateway-api
  • helm template gateway-api ./charts/gateway-api -f ./examples/gateway-api/with-istio-envoyfilter-direct-response.yaml
  • helm template gateway-api ./charts/gateway-api -f ./examples/gateway-api/gateway-api-all-routes.values.yaml
  • helm template gateway-api ./charts/gateway-api -f ./examples/gateway-api/infrastructure-parameters.yaml
  • helm template gateway-api ./charts/gateway-api -f ./examples/gateway-api/minimal.yaml
  • helm template gateway-api ./charts/gateway-api -f ./examples/gateway-api/multiple-httproutes.values.yaml

Made with Cursor

Extend gateway-api chart directResponse handling to support 200-599 statuses (except 403) using Istio EnvoyFilter with optional body defaulting to empty string, while preserving existing 403 AuthorizationPolicy flow.

Made-with: Cursor
@mrdntgrn mrdntgrn merged commit 39525c6 into main Apr 9, 2026
3 checks passed
@mrdntgrn mrdntgrn deleted the 010-gateway-direct-response branch April 9, 2026 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants