メニュー
Diagnose Kubernetes Pod problems such as restarts, CrashLoopBackOff, OOMKilled, Pending, ImagePullBackOff, eviction, health-check failure, and abnormal container exits using Prometheus metrics, VictoriaLogs, and Loki Kubernetes events.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/clcc2019/dsflow --skill k8s-pod-diagnosticコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Calculate incident impact, detection and recovery durations, classify incidents as L0-L3 from service criticality and impact inputs, compute weighted SLA impact and derived availability, and generate post-incident Markdown reports. Use for SLA calculations, incident severity assessment, outage-duration review, availability summaries, postmortems, incident reports, and remediation tracking.
云原生 SRE 值班助理和巡检编排技能。用于基础设施早检、Kubernetes 集群健康检查、Ceph 存储巡检、计算集群巡检、网关故障初筛、异常证据汇总和值班日报生成。触发场景：用户要求早检、巡检、检查集群是否正常、检查 Ceph、检查计算集群、排查网关错误或生成基础设施健康报告。
Create, review, tune, and validate production-grade Prometheus alerting rules and Kubernetes PrometheusRule resources. Use when writing or repairing alert rule YAML, designing PromQL alert expressions, recommending defensible thresholds and for durations, building SLO/error-budget burn-rate alerts, reducing alert noise, standardizing severity/labels/annotations, adding promtool tests, or reviewing an existing Prometheus rule catalog. 用户要求创建、评审或优化 Prometheus 告警规则、PromQL、告警阈值、告警降噪时使用。
| name | k8s-pod-diagnostic |
| description | Diagnose Kubernetes Pod problems such as restarts, CrashLoopBackOff, OOMKilled, Pending, ImagePullBackOff, eviction, health-check failure, and abnormal container exits using Prometheus metrics, VictoriaLogs, and Loki Kubernetes events. |
Use a four-step diagnosis: current state, history, incident window, conclusion. Prefer the bundled scripts before hand-written queries.
scripts/diagnose_pod_restart.sh -c prod-cluster -n <namespace> -p <pod>
scripts/diagnose_pod_restart.sh -c prod-cluster -n <namespace> -p <pod> --window 30
--window is minutes before/after the detected incident time. Default is 15.
# Current Pod state
scripts/check_pod.sh -c <cluster> -n <namespace> -p <pod>
scripts/check_pod.sh -c <cluster> -n <namespace> -p <pod> -f text
# Kubernetes events from Loki/event-exporter
scripts/query_events.sh -c <cluster> -n <namespace> -p <pod>
scripts/query_events.sh -c <cluster> -n <namespace> -p <pod> \
--start 2026-01-21T10:00:00Z --end 2026-01-21T10:30:00Z
check_pod.sh uses Prometheus. query_events.sh uses https://loki.example.com by default.
diagnose_pod_restart.sh: -c/--cluster, -n/--namespace, -p/--pod, --window.check_pod.sh: -c/--cluster, -n/--namespace, -p/--pod, -f/--format, --prometheus.query_events.sh: -c/--cluster, optional -n/--namespace, optional -p/--pod, --start, --end, -l/--limit, -f/--format, --loki-url.OOMKilled or exit code 137: compare memory working set with limit, inspect OOM events and node pressure.CrashLoopBackOff: inspect last exit code, application logs, config/env/secret changes, and startup probes.ImagePullBackOff or ErrImagePull: check image name, tag, registry, pull secret, and network.Pending: inspect FailedScheduling, node resources, taints/tolerations, selectors, affinity, PVC binding.Evicted: inspect node MemoryPressure, DiskPressure, ephemeral storage, and kubelet eviction messages.Unhealthy or Killing: inspect liveness/readiness probe configuration and response latency.Useful event reasons: BackOff, OOMKilling, Failed, FailedScheduling, Killing, TaintManagerEviction, Unhealthy.
prod-cluster: productioncompute-cluster: computetencent-cluster: Tencent TKEaliyun-cluster: Alibaba ACKvictorialogs-analyzer for application/system logs during the locked incident window.k8s-diagnostic when multiple Pods, nodes, or namespaces fail together.Load only when needed:
references/troubleshooting_flows.md: detailed flowcharts.references/common_problems.md: common causes and fixes.references/exit-codes.md: container exit codes.references/prometheus-metrics.md: metric names and query details.references/usage_examples.md: example investigations.references/skill_collaboration.md: cross-skill workflow.