Repository navigation
chore(deps): bump OpenShell to v0.1.5-rhaiv.4 - #810
Open
hypershell-builder[bot] wants to merge 1 commit into
Open
hypershell-builder[bot] wants to merge 1 commit into
hypershell-builder[bot] wants to merge 1 commit into
Conversation
Bump the pinned OpenShell gateway/supervisor/sandbox image tags from v0.1.5-rhaiv.3 to v0.1.5-rhaiv.4 and sweep every dependent file (deployment env vars, capability labels, ROKS e2e defaults, CLI e2e image pin, and the docs/spec citations of the tag). The vendored Helm chart is unchanged (byte-identical between the two tags - this patch only touched Rust source and docs upstream). Flags one contract-affecting change for maintainer decision rather than resolving it silently: upstream NVIDIA/OpenShell#4821 makes the gateway refuse to start when no auth mechanism is configured and allow_unauthenticated_users is not explicitly true, but HyperShell's own ValidateRenderedGatewayConfig still treats that same configuration as well-formed. Documented in openshell-gateway.spec.md's Auth Section and tracked as #809. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
HyperShell environment destroyedThis ephemeral OpenShift environment has been destroyed. Comment |
This was referenced Oct 29, 2026
needs-decision: OpenShell v0.1.5-rhaiv.4 gateway now refuses to start without an auth mechanism
#809
Open
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
This update moves HyperShell's pinned OpenShell gateway from
v0.1.5-rhaiv.3to
v0.1.5-rhaiv.4, the newest stable midstream release. It changes imagetags and version strings only. The vendored Helm chart under
charts/openshell/has no content changes - this patch release only touchedupstream Rust source code and documentation, not the chart.
OPENSHELL_TAGinOPENSHELL_VERSIONand ran the standard sync(deployment env vars, capability labels on four overlays).
pin, and spec/skill doc examples that cite the tag.
make checkdirectly (makeitself cannot run in this agent runtime); all pass.
go build/vet/testcould not run in this runtime (no Go toolchain available) - the CLI e2e
change is a single string-literal image-tag edit, so this is a recorded gap
for CI or a human reviewer to confirm, not a known break.
Release-note triage
Comparing
v0.1.5-rhaiv.3...v0.1.5-rhaiv.4onopendatahub-io/openshell:fix(gateway): require authentication or explicit development opt-in NVIDIA/OpenShell#4821 changes the gateway so it now refuses to start -
before it opens any network port - if no OIDC, mTLS, operator auth, or
gateway_jwtis configured andallow_unauthenticated_usersis not set totrue. Before this change, that same setup just logged a warning and ranunauthenticated. HyperShell's own config check
(
ValidateRenderedGatewayConfig) still accepts that setup as valid today,and the control plane can produce it for a gateway reconciled while
Keycloak integration is off and no custom OIDC issuer is set on the Gateway.
After this bump, such a gateway will crash-loop at startup instead of
running insecurely as before. I filed
needs-decision: OpenShell v0.1.5-rhaiv.4 gateway now refuses to start without an auth mechanism #809 so a maintainer can choose how to handle
it (reject the configuration earlier with a clear error, require an auth
mechanism at gateway-creation time, or default to the old permissive
behavior). This PR does not change that behavior.
SuspendSandbox/ResumeSandboxgRPC calls and two new sandbox states (suspended /suspending) for a new pause-and-resume feature, plus an optional policy
for supervisor middleware extensions. Both changes are backward compatible
and HyperShell does not yet use either feature.
but its image digest cannot be fetched from this runtime (no network
access to
quay.io); this gap is already tracked in needs-decision: bump OpenShell console pin from v0.1.1 to v0.1.2 (digest unresolved) #760 and update-openshell: pin console dashboard v0.1.2 (gateway 0.1.5-rhaiv.1 line) once a digest can be fetched #752.Files changed
OPENSHELL_VERSION,deploy/base/platform-resources/controller.yaml,deploy/{gitops/platform,ibm,kind,openshift}/kustomization.yaml- pin synccomponents/pr-test/e2e-openshell-roks.sh,tests/e2e/cli_test.go- e2eimage pins
specs/platform/data-model.spec.md,specs/platform/openshell-image-auto-update.spec.md,specs/platform/openshell-gateway.spec.md- doc/spec citations of the tag,plus a new note on the auth-gate risk above
skills/deploy/{deploy-cluster,gcp-cluster,ibm-cluster}/SKILL.md- exampleimage pins
skills/tooling/update-openshell/SKILL.md- Learnings log entry and a newpermanent contract-surface check for the gateway startup auth gate
Test plan
make checksub-checks (Python policy scripts and theirunit tests) pass directly
intentional fixtures and historical log entries
go build/vet/test- could not run in this agent runtime (no Gotoolchain); please confirm in CI
including the auth-gate risk above, is still needed