docs(kb-schema-preflight): three-layer KB version preflight guide v1#70
Open
docs(kb-schema-preflight): three-layer KB version preflight guide v1#70
Conversation
Three-layer doctrine for KB version skew (image / chart / live CRD), three typical skew patterns (accidental / engineered / unverified cross-line), and 4-step preflight flow (image digest -> chart render -> CRD storage version keys -> server-side dry-run). Source: 2026-05-05 Oracle BLOCKER #2 final framing - cross-vcluster digest matrix + helm pull chart 1.0.2 inspection proved chart=image=digest 一致 but live CRD differs (separate ApplySet bundle), validating the three-layer model. Companion to existing addon-chart-vs-kb-schema-skew-diagnosis-guide.md (reactive 30-min diagnosis); this doc is the proactive 5-min preflight counterpart. Tom (SQL Server TL) plans v2 extension (§3.5 / §6 / §7 / §8) folding W7 ActionSet env contract drift + KB 1.0.2 isExclusive PoC + cross-engine archetype "chart spec doesn't declare a runtime requirement". v2 will land in this PR as follow-up commits (joint-authored). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
weicao
pushed a commit
that referenced
this pull request
May 5, 2026
7-section preflight for KB addon smoke runs covering: (1) BackupRepo precondition, (2) StorageClass per-vcluster setup, (3) ImagePullPolicy / sideload audit, (4) autopatcher daemon pattern (alpine compatibility), (5) kubeconfig isolation SOP, (6) test-runner artifact directory ready check, (7) vcluster CoreDNS image preflight — newly added based on 2026-05-05 idc4 incident. Section 7 doctrine: if dataprotection / cross-pod-network test cases fail at first run but cluster Running and smoke T01-T07 PASS, check coredns BEFORE addon code. Symptom is pod-level DNS resolution failure but cluster surface looks healthy because exec-based smoke tests do not need DNS. Case study appendix: Oracle 19c T08 ORA-12154 to CoreDNS root cause investigation, image swap fix on idc4 (docker.io/coredns/coredns:1.10.1 ImagePullBackOff swapped to registry.aliyuncs.com/google_containers/coredns:1.10.1 Running 1/1 in 9s). Backup o19-i4-8854-rman19c-w7verify2 Status=Completed, 553MB, 2m32s after fix. One-shot preflight script updated: 7-item check covering all sections + coredns Running validation as item 7. This guide is the proactive "before-smoke" counterpart to first-blocker / smoke result classification doctrine (PR #69). Cross-refs to: - addon-vanilla-vcluster-bootstrap-guide.md (autopatcher + dual-image setup) - addon-idc-vcluster-migration-checklist-guide.md (Alice IDC checklist owner) - addon-kb-schema-version-preflight-guide.md (schema-side preflight, PR #70) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced May 5, 2026
Contributor
Author
|
Curator sweep note (2026-05-06): I scrubbed the PR body hygiene markers through the GitHub API because Remaining merge blocker: commit I am not merging this PR in this sweep because the PR body still lists the v2 extension and co-author tasks as pending. |
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
1 participant
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
addon-kb-schema-version-preflight-guide.md(154 lines) — proactive 5-min preflight counterpart to existingaddon-chart-vs-kb-schema-skew-diagnosis-guide.md(reactive 30-min diagnosis)Source evidence
2026-05-05 Oracle BLOCKER #2 final framing:
helm pull kubeblocks/kubeblocks --version 1.0.2 --untarshows chart 1.0.2 carries NO CRDs (nocrds/dir, no CRD in templates)Evidence file:
phase2-12c-smoke-20260505-113300/01-BLOCKER-2-VERIFICATION-FINAL.txt(Oracle workspace)Joint-authored v2 extension incoming
SQL Server TL plans v2 extension as follow-up commits in this PR (will NOT open separate PR):
§3.5— cross-engine archetype "chart spec doesn't declare a runtime requirement"§6— runtime contract drift evidence pack (per-layer 6-section schema: Symptom / Trigger / Root cause / Reproduction / Fix path / Cross-engine impact + Owner)345bfef9(James)§7— archetype principle + ORA-12154 "double root cause same surface symptom" hook§8— cross-layer decision tree (mermaid)Existing §6/§7/§8 in v1 (保护边界 / 与其他文档关系 / 案例附录) renumber → §9/§10/§11. Case appendix §11 will gain Oracle isExclusive case (existing placeholder filled by Tom) + Oracle W7 ActionSet env drift case + Oracle CoreDNS Layer 2 case.
Curator placement check is requested before drafting v2. Topic boundary remains "addon × KB version-skew + runtime-contract preflight" (no overflow into chaos / dataprotection topical).
Test plan
addon-chart-vs-kb-schema-skew-diagnosis-guide.mdverified (file exists indocs/)addon-componentdefinition-upgrade-guide.mdverifiedaddon-idc-vcluster-migration-checklist-guide.mdverified