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-ingress-gatewaygit 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-ingress-gateway)<a href="https://agentmods.dev/skills/kudig-io/kudig-database/k8s-ingress-gateway"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-ingress-gateway/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-ingress-gateway"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-ingress-gateway.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.04289 |
| Opus 5.5 | $0.00008 | $0.01716 |
| Sonnet 5.5 | $0.00004 | $0.00858 |
| Haiku 4.5 | $0.00002 | $0.00429 |
Grade A, and why
k8s-ingress-gateway scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| SSL 证书错误 | 浏览器或 curl 报错 | 0.95 | How it starts
The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
生产环境安全提示
本文档包含可直接执行的运维命令。执行前请确认：当前目标集群与 Namespace 是否正确；是否具备足够的 RBAC 权限；是否已在非生产环境验证。命令风险等级标注：🔴 高风险（可能造成数据丢失或服务中断）、🟡 中风险（会修改集群状态，但通常可回滚）、🟢 低风险/只读（信息收集，无副作用）。
K8s [[ingress|Ingress]] Gateway Failure 诊断与修复
Ingress 和 Gateway 是 [[kubernetes|Kubernetes]] 集群对外暴露服务的核心机制。配置错误、Controller 异常、后端服务不可达都会导致外部流量无法进入集群。
本 [[SKILL|Skill]] 覆盖 Ingress 规则错误、Gateway API 配置问题、Service 后端不可达、SSL 证书问题等全部常见根因的诊断和修复。
何时使用此 Skill
| 症状 | 检测方法 | 置信度 |
|---|---|---|
| 外部访问返回 502/503 | 直接 HTTP 请求测试 | 0.95 |
| Ingress 地址为空 | kubectl get ingress ADDRESS 列 |
0.90 |
| Gateway 没有 listener | kubectl get gateway |
0.85 |
| SSL 证书错误 | 浏览器或 curl 报错 | 0.95 |
| 路由规则不生效 | kubectl describe ingress |
0.85 |
排除条件: Pod 未运行 → SKILL-POD-001; Service 不通 → SKILL-SVC-001
快速分级（2 分钟内完成）
影响范围
├── 生产入口全部不可用 ──────────→ P0（15min 内修复）
├── 部分路由/域名不可用 ─────────→ P1（30min 内修复）
├── 新 Ingress/Gateway 不生效 ───→ P2（2h 内修复）
└── SSL 证书过期 ────────────────→ P1（30min 内修复）
立即升级条件:
- 所有生产入口同时不可用
- Ingress Controller Pod 全部 CrashLoopBackOff
- 证书过期导致全部 HTTPS 中断
执行流程
# 🟢 低风险：只读/信息收集，通常无副作用
工单/告警触发
│
▼
┌──────────────┐ 脚本: scripts/diagnose-quick.sh
│ Phase 1 │ 内容: kubectl + curl 快速检查（只读）
│ 快速检查 │ Step: D1.1-D1.6
└──────┬───────┘
│ 确认根因
▼
┌──────────────┐ 参考: reference/remediation-playbook.md
│ 修复操作 │ 风险: LOW → MEDIUM → HIGH
│ REM-001~006 │
└──────┬───────┘
│
▼
┌──────────────┐ 脚本: scripts/verify-ingress.sh
│ 验证确认 │ 检查: HTTP/HTTPS 可达性
└──────────────┘
可用脚本
| 脚本 | 用途 | 参数 | 风险 |
|---|---|---|---|
scripts/diagnose-quick.sh |
Ingress/Gateway 快速诊断 | NAMESPACE INGRESS_NAME |
只读 |
scripts/verify-ingress.sh |
修复后验证 | NAMESPACE INGRESS_NAME |
只读 |
根因概览 (6 种)
| RC ID | 根因 | 概率 | 首选修复 | 风险 |
|---|---|---|---|---|
| RC-001 | Ingress/Gateway 规则配置错误 | 高 | REM-001 修正规则 | LOW |
| RC-002 | Ingress Controller 异常 | 高 | REM-002 重启/修复 Controller | MEDIUM |
| RC-003 | 后端 Service 无可用 Endpoints | 高 | REM-003 修复后端服务 | MEDIUM |
| RC-004 | SSL/TLS 证书过期或配置错误 | 中 | REM-004 更新证书 | LOW |
| RC-005 | Gateway API controller 未安装 | 中 | REM-005 安装 controller | MEDIUM |
| RC-006 | DNS 解析不正确 | 中 | REM-006 修正 DNS | LOW |
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 6b934865c51f
- 1mo ago First seen · 326 lines · 21 tokens per session scan A dcdb2307b328
k8s-ingress-gateway 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,289 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
k8s-service-path
Trace the Kubernetes service path — Service to selector to pods to EndpointSlices to readiness, plus Ingress routing. Use when a service is getting no traffic, an ingress is not routing, or someone asks why a workload is unreachable inside a cluster.
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.