Skip to content

docs: fix ClientTrafficPolicy page for targeting all listeners #8892

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
fallard84 wants to merge 1 commit into from
Closed

docs: fix ClientTrafficPolicy page for targeting all listeners #8892

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion site/content/en/v1.5/concepts/gateway_api_extensions/client-traffic-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ kind: ClientTrafficPolicy
metadata:
name: gateway-wide-policy
spec:
targetRefs:
targetSelectors:

@arkodg arkodg May 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this matches the comment - " Policy B: Targets the entire gateway"

- kind: Gateway
name: my-gateway # Targets all listeners
Comment on lines +123 to 125

@chatgpt-codex-connector chatgpt-codex-connector Bot Apr 30, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use valid TargetSelector fields in gateway-wide example

Switching this example to targetSelectors while keeping name makes the YAML inconsistent with the TargetSelector schema (which supports kind, group, matchLabels, and matchExpressions, but not name). In practice this can either be rejected by validation or silently ignore name, causing the policy to match all Gateways of that kind in-scope instead of only my-gateway, which is not what the example text claims.

Useful? React with 👍 / 👎.

timeout:
Expand Down
Loading