Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kudig-io/kudig-databasenpx agentmods add skills/kudig-io/kudig-database/k8s-deployment-rolloutWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kudig-io/kudig-database/k8s-deployment-rollout)<a href="https://agentmods.dev/skills/kudig-io/kudig-database/k8s-deployment-rollout"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-deployment-rollout/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kudig-io/kudig-database/k8s-deployment-rollout"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-deployment-rollout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.04521 |
| Opus 5.5 | $0.00008 | $0.01808 |
| Sonnet 5.5 | $0.00004 | $0.00904 |
| Haiku 4.5 | $0.00002 | $0.00452 |
Grade A, and why
k8s-deployment-rollout scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
生产环境安全提示
本文档包含可直接执行的运维命令。执行前请确认：当前目标集群与 Namespace 是否正确；是否具备足够的 RBAC 权限；是否已在非生产环境验证。命令风险等级标注：🔴 高风险（可能造成数据丢失或服务中断）、🟡 中风险（会修改集群状态，但通常可回滚）、🟢 低风险/只读（信息收集，无副作用）。
K8s Deployment Rollout Failure 诊断与修复
Deployment Rollout Failure 是 [[kubernetes|Kubernetes]] 中最常见的发布问题类型。滚动更新可能因为资源不足、镜像拉取失败、健康检查失败、调度限制等原因卡住，导致新版本无法上线或新旧版本同时运行。
本 [[SKILL|Skill]] 覆盖 Deployment 发布失败、滚动更新卡住、[[replicaset|ReplicaSet]] 残留等全部常见根因的诊断和修复。
何时使用此 Skill
| 症状 | 检测方法 | 置信度 |
|---|---|---|
kubectl rollout status 长时间 pending |
kubectl rollout status deployment/<name> |
0.95 |
| Deployment 的 Available Replicas < Desired | kubectl get deployment |
0.90 |
| Events 中出现 ProgressDeadlineExceeded | kubectl get events --field-selector reason=ProgressDeadlineExceeded |
0.95 |
| 新旧 ReplicaSet 同时存在 | kubectl get rs -l app=<label> |
0.85 |
| Pod 持续处于 Pending/ContainerCreating | kubectl get pods -l app=<label> |
0.80 |
| Deployment 被 paused | kubectl get deployment <name> -o jsonpath='{.spec.paused}' |
0.90 |
排除条件: 节点 NotReady → SKILL-NODE-001; 镜像拉取失败 → SKILL-IMG-001; 权限问题 → SKILL-RBAC-001
快速分级（2 分钟内完成）
影响范围
├── 核心服务（支付/订单/认证）──→ P0（15min 内修复）
├── 生产环境非核心服务 ──────────→ P1（30min 内修复）
├── 预发布/灰度环境 ─────────────→ P2（2h 内修复）
└── 开发/测试环境 ───────────────→ P3（4h 内处理）
立即升级条件:
- 核心服务超过 50% 副本不可用
- Deployment 回滚后仍然失败
- 多个 Deployment 同时出现 rollout 失败
- 发布导致级联问题（依赖服务大量报错）
执行流程
# 🟢 低风险：只读/信息收集，通常无副作用
工单/告警触发
│
▼
┌──────────────┐ 脚本: scripts/diagnose-quick.sh
│ Phase 1 │ 内容: kubectl 快速检查（只读，零风险）
│ 快速检查 │ Step: D1.1-D1.6
└──────┬───────┘
│ 无法确认根因
▼
┌──────────────┐ 参考: reference/diagnostic-workflow.md
│ Phase 2 │ 内容: 深度诊断（只读）
│ 深度检查 │ Step: D2.1-D2.5
└──────┬───────┘
│ 确认根因
▼
┌──────────────┐ 参考: reference/root-cause-catalog.md
│ 根因匹配 │
│ RC-001~007 │
└──────┬───────┘
│
▼
┌──────────────┐ 参考: reference/remediation-playbook.md
│ 修复操作 │ 风险: LOW → MEDIUM → HIGH
│ REM-001~006 │
└──────┬───────┘
│
▼
┌──────────────┐ 脚本: scripts/verify-deployment.sh
│ 验证确认 │ 检查: Rollout 状态/Pod 状态/RS 清理
└──────────────┘
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +19 lines 6e554c7bf4b3
- 1mo ago First seen · 337 lines · 21 tokens per session scan A 39c5f35601ed
k8s-deployment-rollout is a skill published in the GitHub repository kudig-io/kudig-database (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 4,521 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
networkpolicy-debug
Diagnose NetworkPolicy-related connectivity issues (traffic unexpectedly blocked, default-deny effects, egress blocking DNS). Identifies which NetworkPolicies affect a pod, checks ingress/egress rules, and verifies CNI support.
statefulset-debug
Diagnose StatefulSet rollout and scaling failures (ordered update stuck, OnDelete not updating, partition misconfiguration, PVC binding deadlocks). Checks update strategy, pod ordinal progression, PVC bindings, and ordered startup to identify why a StatefulSet is not progressing.
image-pull-debug
Diagnose container image pull failures (ErrImagePull / ImagePullBackOff). Checks pod status, containerd logs, and events to identify root cause.
pod-pending-debug
Diagnose pod scheduling failures (Pending, Unschedulable). Checks events, node resources, taints, affinity, and PVC bindings to identify why a pod cannot be scheduled.
deployment-rollout-debug
Diagnose Deployment rollout failures (stuck rollouts, ProgressDeadlineExceeded, replica mismatch). Checks rollout status, ReplicaSets, and new pod health to identify why an update is failing.
pod-crash-debug
Diagnose pod crash failures (CrashLoopBackOff, OOMKilled, Error, RunContainerError). Checks pod status, events, and previous logs to identify root cause.