I treated Kubernetes like a company and gave it a brain

说明与用途

该系统将 Kubernetes KEP 状态与其 GitHub 记录同步，识别出 40 个僵尸提案，并提供准确、时间过滤的查询以及带有草拟修复建议的审计页面。

问题

Kubernetes KEPs and their tracking issues drift apart, leaving many proposals in a zombie state where status records are inconsistent and hard to reconcile.

结果

The system identifies 40 zombie KEPs, provides accurate, time‑filtered status queries, and offers an audit page with drafted fixes, all while ensuring answers are fully cited and verifiable.

工作流

• 1. Pull KEPs, SIG rosters, OWNERS files, issues and PR history from GitHub.
• 2. Load data into FalkorDB as a graph, preserving status edges with timestamps.
• 3. Run daily sync to keep graph up‑to‑date.
• 4. Expose a read‑only agent that answers plain‑English questions via GRAPH.RO_QUERY with timeouts.
• 5. Validate each answer’s citations against graph nodes; discard answers with missing or incorrect citations.
• 6. Provide an audit page that lists all record disagreements and drafts fixes.
• 7. Allow maintainers to review and manually resolve discrepancies.

证据

Kubernetes has proposals that are officially "implementable" while their tracking issue was closed back in 2019.

来源

I loaded three SIGs (sig-node, sig-scheduling and sig-apps), 238 KEPs in total. The result: 59 pairs of records disagreeing across 50 KEPs, and 40 of those zombies.

来源

A worker pulls everything live from GitHub: KEPs, SIG rosters, OWNERS files, issues and PR history. It all becomes one graph of about 39,000 nodes and 127,000 edges, and it re-syncs every day.

来源

Every answer cites its sources, and each citation is a graph node with a GitHub link you can click.

来源