菜单
Use when checking Kubernetes manifests for deprecated or removed APIs, planning K8s version upgrades, or migrating manifests to newer API versions. Also use when another K8s review skill flags deprecated APIs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | kubernetes-deprecation-check-and-upgrade |
| description | Use when checking Kubernetes manifests for deprecated or removed APIs, planning K8s version upgrades, or migrating manifests to newer API versions. Also use when another K8s review skill flags deprecated APIs. |
Comprehensive API deprecation audit with migration guidance, testing requirements, and local validation paths. Scans manifests, Helm templates, and Kustomize bases for deprecated or removed Kubernetes API versions, provides concrete migration steps, calls out breaking changes, and recommends validation approaches including local Kind cluster testing.
Triggered by direct user request for upgrade/version checks, or as a cascading recommendation from other K8s review skills (security-audit, operational-review, helm-review, kustomize-review) when they detect deprecated APIs.
apiVersion and kind from each resource.deprecation-tables.md to determine if the API version is deprecated or removed in the target version.pathType is required in networking.k8s.io/v1.extensions → networking.k8s.io).migration-guide.md).kubeconform or kubeval against the target K8s version schema.kubectl apply --dry-run=server against a cluster running the target version. For Helm charts, also helm template + helm lint. For Kustomize, also kustomize build.migration-guide.md for exact commands and fallback options when Kind is unavailable.migration-guide.md.extensions/v1beta1 or networking.k8s.io/v1beta1| Mistake | Why It Happens | Correct Approach |
|---|---|---|
| Scanning only top-level manifests | Helm templates and Kustomize bases are missed | Scan rendered templates (helm template), Kustomize bases, and raw manifests |
| Not checking CRD compatibility | Focus on core K8s APIs only | Third-party CRDs (cert-manager, Istio) have their own deprecation cycles |
| Recommending Kind cluster without checking target version availability | Not all K8s versions have Kind node images | Check kindest/node tags for available versions |
| Ignoring RBAC group changes | API group changes affect RBAC rules too | If extensions → networking.k8s.io for Ingress, update RBAC rules referencing extensions |
| Migrating all at once | Big-bang migration is risky | Recommend incremental migration: non-breaking changes first, then breaking ones |
| Not flagging webhook compatibility | Admission webhooks may reject new API versions | Check ValidatingWebhookConfiguration and MutatingWebhookConfiguration for API version filters |
deprecation-tables.md — API deprecation matrix by Kubernetes version (1.22 through 1.32)migration-guide.md — Rollback strategies, migration ordering, dependency checklists, Kind cluster validation guideUse when a skill needs step tracking, progress visibility, and resume support within a single phase. Called by skills, not directly by users.
Use when breaking down a project phase into stories with acceptance criteria, creating ADRs, or planning infrastructure work. Triggers on /plan, story breakdown, detailed plan, architecture doc.
Use when generating, editing, or merging Low-Level Design (LLD) documents at `docs/lld/<component>.md` or `docs/shield/<feature>/lld-<component>.md`. Triggers on /lld command (Path A) and on /plan TRD-driven authoring (Path B, M2 plan). Owns the backend and infra templates, atomic write, provenance stamp, and §14 Changelog convention.
Use when authoring a new PRD or upgrading a lean PRD to standard. Walks user through 20-section problem-first scaffold (or 10-section lean), pre-populates from prior /research transcript if present, defers Terminologies (§2) until after the rest is drafted (auto-fills from research glossary + scan of body), invokes shield:story-coverage between Sections 6 and 8 and shield:milestone-coverage between Sections 8 and 15, prompts for story Type (new/enhancement/existing), supports custom team templates via .shield.json. Triggers on /prd, write a PRD, author a PRD.
Use when the user invokes /backlog or asks to capture, view, promote, or remove an idea from the project backlog at docs/shield/backlog.json. Triggers on /backlog add|view|remove|promote and on agent-side "capture this as a backlog entry" calls during research/PRD/plan/implement flows.
Use when a plan, architecture doc, or execution plan exists and needs expert review before implementation. Produces a scored analysis with a P0-gated verdict and an enhanced plan. Triggers on /plan-review, review my plan, document review.