Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Independent verification against the cited upstream source remains incomplete, so the operational guidance needs human confirmation.
1 open finding
What changed in this PR
Adds endpoint publishing and verification workflows to the Stacklok Enterprise gateway documentation.
Changes:
- Documents gateway routing, TLS, streaming, and separate API checks.
- Explains Service CIDR discovery and failed-connector recovery.
- Links deployment, client rollout, and API references to publishing guidance.
| File | Description |
|---|---|
| docs/platform/enterprise-platform/roll-out-gateway-clients.mdx | Adds publishing prerequisites. |
| docs/platform/enterprise-platform/deployment.mdx | Links gateway publishing workflows. |
| docs/platform/enterprise-platform/configure-connector-gateway.mdx | Adds routing and authentication checks. |
| docs/platform/enterprise-platform/configure-ai-gateway.mdx | Adds inference publishing and API verification. |
| docs/connector-gateway/connectors.mdx | Explains network allowlists and recovery. |
| docs/connector-gateway/api-reference.mdx | Links Connector Gateway publishing guidance. |
| docs/ai-gateway/api-reference.mdx | Links AI Gateway publishing guidance. |
🧠 Review effort: Balanced
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
Operators could enable the gateways without instructions for publishing usable client endpoints, and discovered Kubernetes connectors still required operators to infer the cluster's verification allowlist and recovery steps. Add publishing and verification sections to both gateway deployment guides, plus Service CIDR discovery and failed-connector recovery to Manage connectors.
errfield, as observed during live validation.Validation
Production build, Prettier, ESLint, and
git diff --checkpass. Publishing YAML parses, and the AI Gateway configuration fields and enum values match the source CRD. Service targets, ports, routing, and verification behavior were checked againststacklok-enterprise-platformata711b3e256fe515675f41de0b7aa36498be4a3f2.Live tests passed on
kind-stacklok-enterprise-demowith platform chart0.21.0:10.96.0.0/16; the configured verification allowlist matched it.failuredespiteallow_private_ips: true. Re-saving with an allowed Service endpoint producedavailable.Temporary Kubernetes resources, connectors, connections, and OAuth registrations were cleaned up; the original gateways remained healthy. No Helm upgrade or Claude Code UI workflow was performed. The MCP flow was exercised directly.
Type of change
Related issues/PRs
Closes #1161.
Closes #1217.
Partially addresses #1159 by adding endpoint publishing and separate registration, control-plane, and MCP verification. Its remaining identity configuration and platform-admin grant gaps are outside this PR.
Submitter checklist
Content and formatting
Reviewer checklist
Content