Repository navigation
docs: align Registry v2 migration runbook with release 4.5 - #864
Merged
Merged
Conversation
zhhray
force-pushed
the
codex/update-registry-v2-migration-runbook
branch
from
November 2, 2026 10:34
9735fef to
aae6e21
Compare
Restructure the runbook around a stage overview and add the checks that were missing where a mistake cannot be undone. - add a stage table with interruption and re-run columns - fail closed when an Ingress UID drifts in P5 instead of deleting it - snapshot the Secret list before the chart uninstall in P5 - refuse to record P2 when the maintenance record is missing - pass the CA bundle to ac through SSL_CERT_FILE in P8 - assert the storage management state in P7 and P8 - compare digest sets with comm instead of counting rows - split the appendix into known limitations and retries/recovery
Split long interactive functions into short Bash blocks with explicit results and failure checks. Validate compatibility inventory output as exactly one JSON array and prevent delete previews after failed or incomplete queries. Clarify the compatibility client's Registry TLS verification limitation and retain verified HTTPS, OCI-client, and kubelet checks for acceptance.
PR checks compared untouched generated translations with updated English before the main-only translation step could regenerate them. Check changed translations and manual translations on PRs, while keeping post-translation validation strict. Add regression tests for source-only edits, changed pairs, and manual-translation opt-outs.
This branch was successfully 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
The Registry v2 migration runbook now reflects the release-4.5 Operator and
accompatibility contract.Changes
readOnly, storageUnmanaged, pull-secretUnmanaged, and suspended Pruner state before import.ImageDigestand static namespace LimitRange verification.ac4.3 output contract,AC_REGISTRY_COMPAT_OUTPUT, explicit Registry URL behavior, original 4.3 client limitations, and platform-admin prune/GC boundary./v2/authentication realm so an unreachable challenge host or port cannot be mistaken for a healthy endpoint.Validation
git diff --checkcluster-image-registry-operatorrelease-4.5 (a51a2183) andacrelease-4.5 (2c00a8d9)