Skip to content

docs: target Envoy route by JSONPath - #829

Open
woodgear wants to merge 1 commit into
alauda:mainfrom
woodgear:docs/envoy-patchpolicy-route-jsonpath
Open

docs: target Envoy route by JSONPath#829
woodgear wants to merge 1 commit into
alauda:mainfrom
woodgear:docs/envoy-patchpolicy-route-jsonpath

Conversation

@woodgear

@woodgear woodgear commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • document the two-step workflow: inspect the HTTPRoute YAML/status to find the accepted Gateway listener, then create the EnvoyPatchPolicy
  • define one HTTPRoute rule as the exact patch target and select every generated match route for that rule
  • explain each JSONPath token and use explicit VAR_$... placeholders
  • require users to replace every placeholder before applying the policy
  • include a fully resolved PatchPolicy example with concrete Gateway, HTTPRoute, listener, rule, and authority values
  • document that EnvoyPatchPolicy JSONPath support starts in Envoy Gateway v1.2.0
  • keep the change scoped to the English document

Verification

  • parsed every changed YAML example with yq
  • validated the kubectl get httproute ... -o yaml command syntax
  • verified the selector includes all matches for the target rule and excludes another rule
  • ran git diff --check
  • ran yarn build successfully

@woodgear
woodgear deployed to translate August 11, 2026 03:18 — with GitHub Actions Active
@woodgear
woodgear force-pushed the docs/envoy-patchpolicy-route-jsonpath branch from 1420d99 to f5fe5bb Compare August 11, 2026 03:29
@woodgear
woodgear deployed to translate August 11, 2026 03:29 — with GitHub Actions Active
@woodgear
woodgear force-pushed the docs/envoy-patchpolicy-route-jsonpath branch from f5fe5bb to 637e9fc Compare August 11, 2026 03:42
@woodgear
woodgear deployed to translate August 11, 2026 03:42 — with GitHub Actions Active
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