Repository navigation
feat(helm)!: require opt-in for gateway service routing - #5672
Draft
TaylorMutch wants to merge 3 commits into
Draft
TaylorMutch wants to merge 3 commits into
TaylorMutch wants to merge 3 commits into
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
🌿 Preview your docs: https://nvidia-preview-pr-5672.docs.buildwithfern.com/openshell |
BREAKING CHANGE: Helm installations relying on gateway service URLs must explicitly set gatewayConfig."openshell.gateway".service_routing_enabled to true before upgrading. Core and non-Kubernetes defaults remain unchanged. Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
Signed-off-by: Taylor Mutch <taylormutch@gmail.com>
TaylorMutch
force-pushed
the
feat/5671-helm-service-routing-opt-in/TaylorMutch
branch
from
November 18, 2026 05:50
c6e1b4f to
f947299
Compare
TaylorMutch
force-pushed
the
feat/4953-authoritative-app-urls/TaylorMutch
branch
from
November 18, 2026 05:51
b7042a9 to
1e069a1
Compare
This branch has not been 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.
Summary
Default Kubernetes Helm deployments to disabling gateway-mediated sandbox service routing, avoiding an unintended alternate application access path when operators use dedicated application ingress. The core runtime keeps its enabled default, preserving Docker, Podman, and VM behavior outside this chart.
Upgrade action: Helm installations relying on gateway service URLs must explicitly retain forwarding:
Based on #4956. This draft changes Helm behavior separately from the URL and gateway application-auth PRs.
Related Issue
Closes #5671.
Changes
service_routing_enabled = falseby default, including saved values that omit the setting or set it to null; preserve explicit boolean choices.[openshell.supervisor.app_listener].enabled = trueplus an ingress solution that routes discovered hostnames to the owning supervisor app-listener endpoint. Usebase_urlas the only application origin, with its domain derived automatically. Include the Helm/TLS configuration example, explicit gateway opt-in, and upgrade setting.Testing
mise run helm:test: chart unit suites, rendered TOML loader validation, object ownership, resource coherence, supervisor scaling, and autoscaling checks.mise run helm:docs:checkandmise run markdown:lint. The exact documented app-listener Helm example renders and passes gateway config preflight.base_urlexample and matching local images. The shared case also passed graceful owner takeover; the dedicated case passed gateway-outage expiry.Release Notes
Kubernetes Helm deployments now require an explicit opt-in for gateway-mediated sandbox service URLs and HTTP/WebSocket forwarding. Set
gatewayConfig."openshell.gateway".service_routing_enabled: truebefore upgrading if you rely on that path. The core and non-Kubernetes defaults are unchanged.