Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add kudig-io/kudig-database --skill k8s-dns-failuregit clone --depth 1 https://github.com/kudig-io/kudig-databaseWrote 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-dns-failure)<a href="https://agentmods.dev/skills/kudig-io/kudig-database/k8s-dns-failure"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-dns-failure/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-dns-failure"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-dns-failure.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.00000 | $0.03567 |
| Opus 5.5 | $0.00000 | $0.01427 |
| Sonnet 5.5 | $0.00000 | $0.00713 |
| Haiku 4.5 | $0.00000 | $0.00357 |
Grade A, and why
k8s-dns-failure 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- k8s-performance — 86% identical, 308 lines differ
How it starts
The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
生产环境安全提示
本文档包含可直接执行的运维命令。执行前请确认：当前目标集群与 Namespace 是否正确；是否具备足够的 RBAC 权限；是否已在非生产环境验证。命令风险等级标注：🔴 高风险（可能造成数据丢失或服务中断）、🟡 中风险（会修改集群状态，但通常可回滚）、🟢 低风险/只读（信息收集，无副作用）。
DNS 解析问题诊断与修复
概述
[[coredns|CoreDNS]] 是 [[kubernetes|Kubernetes]] 集群 DNS 的核心组件。DNS 问题会导致服务发现失败、外部依赖不可访问等连锁问题。
典型触发场景：
- CoreDNS Pod 崩溃或资源不足
- CoreDNS ConfigMap 配置错误
- [[networkpolicy|NetworkPolicy]] 阻断 UDP/53
- 节点 DNS 配置冲突（systemd-resolved 等）
症状识别
| # | 症状描述 | 检测方法 | 置信度 |
|---|---|---|---|
| S1 | Pod 内域名解析失败 | nslookup kubernetes.default |
0.95 |
| S2 | 跨服务调用超时 | 应用日志显示连接超时 | 0.80 |
| S3 | CoreDNS Pod 未 Running | `kubectl get [[Pods | pods]] -n kube-system` |
快速诊断
./scripts/diagnose-quick.sh <namespace> [pod-name] [test-domain]
修复动作
低风险修复
| # | 修复动作 | 命令 |
|---|---|---|
| R1 | 重启 CoreDNS Pod | kubectl rollout restart deployment coredns -n kube-system |
| R2 | 扩大 CoreDNS 副本数 | kubectl scale deployment coredns -n kube-system --replicas=3 |
| R3 | 修正 Pod dnsPolicy | kubectl patch pod <pod> --type merge -p '{"spec":{"dnsPolicy":"ClusterFirst"}}' |
中风险修复
| # | 修复动作 | 风险 |
|---|---|---|
| R4 | 修改 CoreDNS ConfigMap | 配置错误可能导致全集群 DNS 问题 |
| R5 | 修改节点 resolv.conf | 可能影响节点上所有容器 |
验证修复
./scripts/verify-dns.sh <namespace> [pod-name] [test-domain]
升级条件
- 修复后 DNS 仍间歇性失败 → 升级至网络深度诊断
- 怀疑 CNI 问题 → 升级至 SKILL-NET-003
远程顾问信息收集
作为远程顾问，我无法直接连接你的集群。请帮我收集以下信息，我会根据你提供的内容给出准确的诊断建议。
第一步：快速确认（30 秒内回答）
- 影响范围：这个问题影响多少个节点 / Pod / 命名空间？
- 紧急程度：业务是否已中断？是否有用户投诉？
- 发生时间：问题是突然发生还是逐渐恶化？最近是否有变更？
第二步：关键信息（请提供你能获取的）
- kubectl 版本：
kubectl version --short的输出 - K8s 集群版本：
kubectl get nodes -o wide中的 VERSION 列 - 节点状态：控制平面节点是否正常？工作节点是否正常？
第三步：诊断信息（按需补充）
如果以下命令你无法执行，请直接告诉我「无法执行」，我会提供替代方案。
- 相关组件日志：
kubectl logs -n <namespace> <pod>的最后 30 行 - 节点资源：
kubectl top nodes或kubectl describe node <node>的 Capacity/Allocated resources - 近期变更：最近 24 小时是否有部署、扩缩容、配置变更？
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 082d0d5e30cf
- 1mo ago First seen · 276 lines · 0 tokens per session scan A 9d893a5568fe
k8s-dns-failure is a skill published in the GitHub repository kudig-io/kudig-database (6 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,567 tokens. 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
cluster-events
Analyze cluster-wide Kubernetes events to identify issues and patterns. Aggregates Warning events, detects high-frequency patterns, and correlates related events.
ingress-debug
Diagnose Ingress failures (rules not matching, backend unreachable, TLS errors, no address assigned). Checks Ingress resources, IngressClass, backend Services, and controller health to identify why external traffic is not routed correctly.
quota-debug
Diagnose Kubernetes native ResourceQuota and LimitRange admission rejections (exceeded quota, forbidden by LimitRange, FailedCreate). Checks namespace quotas, current usage, LimitRange constraints, and ReplicaSet events to identify why pods cannot be created. Not applicable to Volcano Queue — use…
volcano-diagnose-pod
Diagnose Volcano-managed Pod scheduling issues. Checks Pod status, PodGroup, events, and Queue to identify scheduling failures.
volcano-job-diagnose
Diagnose Volcano Job status and issues. Check Job phases, task statuses, PodGroup associations, and overall job health.
volcano-queue-diagnose
Diagnose Volcano Queue status and resource allocation. Check queue weights, deserved resources, allocated resources, and identify queue-related scheduling bottlenecks.