Repository navigation
Refresh component versions and offline examples for 26.11 - #1428
Merged
Merged
Conversation
Update monitoring, registry proxy and Slurm pins from public upstream releases. Keep the registry-cache example aligned with its role default. Leave Network Operator and MIG Manager unchanged pending verification. Signed-off-by: Doug Holt <[email protected]>
Keep Slurm archives and monitoring pull, save, mirror and override examples aligned with the selected 26.11 component defaults. Signed-off-by: Doug Holt <[email protected]>
Default kube-prometheus-stack to 88.6.5 so monitoring meets the minimum version required by Run:ai platform mode. Signed-off-by: Doug Holt <[email protected]>
Use published stable releases and align offline download examples. Select Network Operator 26.7.0, the newest chart currently published in the configured repository, rather than its newer source-only release. Retain the monitoring chart floor pending major-upgrade review. Co-Authored-By: Paperclip <[email protected]> Signed-off-by: Doug Holt <[email protected]>
Preserve the version-refresh commits while integrating current master. Retain Slurm 26.05.5 alongside the upstream opt-in Lua build setting. Co-Authored-By: Paperclip <[email protected]> Signed-off-by: Doug Holt <[email protected]>
Mirror GPU Operator v26.7.2 and registry 3.1.2 consistently across connected-side preparation, transfer records, and offline imports. Add regression checks against role defaults, including the explicit driver override. Retain R580 to avoid an unvalidated driver-branch upgrade as part of the chart refresh. Co-Authored-By: Paperclip <[email protected]> Signed-off-by: Doug Holt <[email protected]>
Preserve the version refresh while incorporating the latest upstream changes. Co-Authored-By: Paperclip <[email protected]>
Include the driver role update and monitoring failure handling while preserving the reviewed version-refresh commits. Signed-off-by: Doug Holt <[email protected]> Co-Authored-By: Paperclip <[email protected]>
Preserve the current monitoring installer and all remaining version refresh changes without rewriting existing commits.
dholt
marked this pull request as ready for review
November 3, 2026 16:28
michael-balint
approved these changes
Nov 4, 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.
Summary
Refresh published component versions and keep offline preparation aligned with role defaults:
Validation
On integration head
6a3cee6d20208759fa369f134f284a944d3c1181:Earlier live QA, not rerun on this integration head:
ef258397, Slurm 26.05.5 build, an A30 GPU job viasrun, a Pyxis container GPU job, login GPU guard and Slurm exporter checks passed with driver 580.178.04.a1e1f4cb, single-node Kubernetes, GPU Operator and a GPU pod runningnvidia-smipassed with an A40 and preinstalled driver 580.178.04.QA limits
docs/k8s-cluster/monitoring-upgrade-92.md; a plain Helm upgrade is not a substitute for the CRD-first procedure.Ready for maintainer review; the QA limits above still apply.