Repository navigation
Conversation
Use rotating projected credentials for control-plane scraping instead of a non-expiring token Secret. Document pinned CRD migration from 88.6.5 and verify both site-value examples with offline Helm renders. Co-Authored-By: Paperclip <noreply@paperclip.ing>
Merge reviewed saved user values before target site settings, document image-key migration, and cover token TLS wiring and all reset CRDs. Co-Authored-By: Paperclip <noreply@paperclip.ing>
Map installer mirror references to the effective chart image objects, preserving registry ports, nested paths, tags and digests. Exercise the installer arguments through the exact chart's offline render. Refuse existing unhealthy releases and lookup errors before workload changes. Use plain install for missing releases, leaving upgrades and failed-release recovery to the reviewed exact-package CRD-first guide. Co-Authored-By: Paperclip <noreply@paperclip.ing>
Allow reviewed Helm-owned field conflicts with a dry-run-first retry. Stop on failed recovery commands and require all ten CRD version annotations to match the operator before upgrading workloads. Co-Authored-By: Paperclip <noreply@paperclip.ing>
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
Prepare the monitoring chart upgrade for DeepOps 26.12, not 26.11.
helm install; healthy releases continue to skip installation.Validation
Evidence boundaries and limitations
Live chart/configuration tests used the preceding commit; the chart and both monitoring value files are unchanged in the final installer fix. Final mirror mapping and fail-closed installer behavior have behavioral and exact-chart render test coverage, not live installer coverage. Live tests used direct Helm and the documented CRD-first procedure.
The GPU test device could not expose NVLink or PCIe profiling counters; those panels had no data on either version. Existing non-GPU endpoint failures and node-exporter port conflicts were identical on the baseline and target, not new regressions. Multi-node placement, external scrapers and rollback were not live-tested. Run:ai's 88.6.5 numeric chart floor is satisfied; runtime compatibility is not certified.
Mirror mappings are render-verified for 92.14.0 only. Auxiliary images require separate site configuration. Existing site values must be reviewed and migrated; do not blindly reuse old chart defaults or delete CRDs for recovery.