Repository navigation
Set the gateway pod selector in AI Gateway example - #1364
Merged
Merged
Conversation
The ai-gateway-v2 chart no longer defaults the NetworkPolicy ingress to Envoy Gateway, and refuses an enabled policy with no pod selector. Name the selector in the example so it renders on the current and the next chart. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The documented value paths omit networkPolicy, which can cause readers to configure the wrong keys and leave required selectors unset.
1 open issue
What changed in this PR
Updates the AI Gateway configuration guide so its network policy example explicitly supplies the gateway pod selector required by the upcoming chart.
Changes:
- Adds an Envoy proxy pod selector to the YAML example.
- Explains how the pod selector and namespace list control ingress.
| File | Description |
|---|---|
docs/platform/enterprise-platform/configure-ai-gateway.mdx |
Adds the gateway pod selector and clarifies ingress selection. |
Review effort: Balanced
Comment on lines
+307
to
+311
| - **Ingress** admits only the pods that match `ingress.gatewayPodSelector` in | ||
| `ingress.gatewayNamespaces`. Set both to your Gateway's data plane. The | ||
| example uses Envoy Gateway's proxy pods. `ingress.gatewayNamespaces` must not | ||
| be empty. The metrics port is admitted from `ingress.monitoringNamespaces` | ||
| when Prometheus metrics are on. |
Member
Author
There was a problem hiding this comment.
Good catch, fixed in a996b4c. The ingress bullet now uses the full networkPolicy.ingress.* paths, including monitoringNamespaces, which matches the egress bullet and the page's convention.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
peppescg
approved these changes
Nov 20, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Description
The
ai-gateway-v2chart no longer defaults the NetworkPolicy ingress to Envoy Gateway. stacklok/stacklok-enterprise-platform#6921 emptiesnetworkPolicy.ingress.gatewayNamespacesandgatewayPodSelector, and the render refuses an enabled policy with no pod selector. The example in "Restrict network access" sets onlygatewayNamespaces, so it fails on that chart.This PR adds
gatewayPodSelector: {app.kubernetes.io/name: envoy}to the example and says what the two keys select. The example renders the same NetworkPolicy on the current chart, where that selector is already the default, and works on the next one.The Helm reference page (
reference/helm/ai-gateway.mdx) still lists the old defaults. It's generated from the chart at release, so I left it alone.Type of change
Related issues/PRs
Submitter checklist
Content and formatting
🤖 Generated with Claude Code