Record installed UDS Core 1.13.1 and operator CLI 0.39.0 #46
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/Documentation!46
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/uds-version-documentation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Record the owner's 2026-10-14 confirmation that Core v1.13.1 is installed and operator UDS CLI v0.39.0 was just installed. Reconcile the platform overview, architecture, decisions, delivery history and source register; preserve original versions in dated scan/test evidence and distinguish the operator CLI from Actions' reviewed 0.38.0 pins.
Future Core upgrades retain Harbor setup and owner acceptance as a prerequisite, with sequential minor upgrades to the latest stable target selected when work starts. No pipeline tool pin or cluster resource changes are included.
Validation: npm run check and npm run build passed; git diff --check passed; the native Gitleaks 8.30.1 pre-commit scan found no leaks. This records owner-reported versions rather than a new live health audit.
Reviewed the five-file documentation diff and exact-head source. The 2026-10-14 owner-reported Core 1.13.1/operator CLI 0.39.0 baseline is consistently labeled as a report, not a fresh health/deployment audit; historical 1.11.1 and 0.38.0 run evidence remains dated, and the separate Actions CLI pins are explicitly unchanged. Harbor setup and owner acceptance stay prerequisites for later sequential Core upgrades. This PR changes documentation only, not bundles, rendered resources, Istio gateway ownership, admission policy or scan gates; no additional UDS deployment validation is triggered by this diff. Source review approved. At review time, site validation and source security were still running, while the security pipeline wrapper was blocked by its prerequisite: those required checks remain independent merge gates, not verified passes. No merge authorized.
CI at submission: pending. This is a source-review approval, not a scan verdict; required checks still block merge.