fix: verify chart access and surface repository readiness - #242
Merged
Merged
Conversation
Contributor
Author
Contributor
Author
…g credentials A working Helm/OCI chart download commonly 302s to object storage or a CDN on a different host. The chart probe refused any cross-origin redirect, reporting a healthy repository as broken. Allow cross-host redirects while keeping the TLS-only and redirect-limit guards, and strip the Authorization header before the request leaves the requested origin so the registry credential is never forwarded to another host.
The chart-access check sampled the alphabetically-first chart from each repository index. For gated NGC team repositories that first chart is often one absent from the curated catalog or one the customer is not entitled to, so the probe returned a spurious 403 for a repository that is actually usable. Add catalog.RepresentativeChart, which selects the first supported catalog chart a repository serves (falling back to its first entry, then to a well-known sample for mirrors not in the catalog), and use it for every connected-mode source. An explicit chart name from the form still wins.
…-readiness # Conflicts: # ui/package-lock.json # ui/package.json
Contributor
rewenila
approved these changes
Sep 21, 2026
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.











Problem
A successful registry login can coexist with denied chart access or a disconnected Rancher ClusterRepo. Kubeflow, LiteLLM and Qdrant then fail on the first wizard page with
configmaps "" not found. NVIDIA repositories can also return a public index while denying a chart download, or return an invalid index that Rancher reports asno API version specified.Changes
A successful test covers only the displayed sample chart/version and Rancher index readiness. It does not verify all charts, full chart downloads, container images or installation prerequisites.
Validation
78c6e8e0: 267 UI tests (including 21 verification component tests using real Rancher components), lint, typecheck and the production extension build passed locally. UI CI passed on this commit. Chromium checks covered seven result scenarios in light/dark themes, keyboard Test, changed chart inputs, Refresh Pending → Ready, and narrower widths down to 390 px. The complete Settings page used real components, fonts and Rancher styles with fixture API responses; there were no external requests or browser errors. These screenshots are local previews; no environment was redeployed for this styling change.ec14fee7: both GitHub CI workflows passed; 267 UI tests, lint and typecheck passed. Exact-source operator/UI images and Helm charts built successfully. Operator build, envtest and targeted API/credential-check race tests passed during implementation. The following live results refer to that revision.