Behavioural Process Intelligence · Public Mirror
Kubernetes
What we read from 286 public GitHub events across the last 13 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Kubernetes · May 9, 2026
9 PRs merged with no independent review.
9 PRs merged with no independent review. Spans 3 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
kubernetes/kubernetes#138921·kubernetes/kubernetes#138764·kubernetes/kubernetes#138740·kubernetes/kubernetes#138915·kubernetes/k8s.io#9458
k8s-ci-robot authored 7/7 commits in kubernetes/kubernetes. 100% concentration in this window. If k8s-ci-robot stops, kubernetes/kubernetes stalls.
15 PRs merged between 22:00 and 06:00 UTC. Spans 5 repos. Either an always-on global org or a deploy-late-night habit.
kubernetes/kubernetes#138921·kubernetes/kubernetes#138764·kubernetes/kubernetes#138740·kubernetes/website#55697
11 PRs merged on a weekend. Across 4 repos. Could be on-call work, could be habit drift.
kubernetes/kubernetes#138921·kubernetes/kubernetes#138764·kubernetes/kubernetes#138740·kubernetes/website#55697
kubernetes/kubernetes carried 52% of activity. 150 of 286 events in the last 13 weeks. Next: kubernetes/website (66).
1 issue opened, 79 issue comments. Issue traffic is 2.1× the code traffic this window — consumer-facing org or triage burst.
FIG 2 · Activity stats
FIG 3 · Repos by activity
- kubernetes/kubernetes150 events · 7 commits · 7/1 PRs
- kubernetes/website66 events · 5 commits · 5/2 PRs
- kubernetes/kops16 events · 1 commit · 1/1 PRs
- kubernetes/test-infra11 events · 0 commits · 0/1 PRs
- kubernetes/k8s.io9 events · 1 commit · 1/0 PRs
- kubernetes/minikube7 events · 0 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @k8s-ci-robot144 events · 51% share
- @liggitt36 events · 13% share
- @windsonsea12 events · 4% share
- @k8s-triage-robot9 events · 3% share
- @jpbetz8 events · 3% share
- @tallclair6 events · 2% share
FIG 5 · Rituals we can't see from GitHub alone
Public-GitHub data shows code behaviour. The rituals below need the rest of the toolchain. With Slack, Linear, Notion and Google connected, Assemblr would also surface:
Silent merge · PR merged with no Slack/release-notes followup within 30 min.
Needs: Slack #releases channel
Orphan ticket · Linear issue closed without a corresponding code merge in 7 days.
Needs: Linear (or Jira) to see ticket transitions
Ladder break · Cross-toolkit ritual fires N-1 of N expected steps for ≥3 occurrences.
Needs: Linear + Slack to stitch the cross-tool ladder
Stale-design code · Code shipped where the linked design doc hasn't been touched in 30+ days.
Needs: Notion or Google Docs for design-doc edit history
Postmortem skip · Incident channel created, no postmortem doc within 7 days of resolution.
Needs: Slack incident channels + Notion postmortem template
Phantom standup · Standup channel post pattern that ran ≥4 weeks then stopped ≥7 days ago.
Needs: Slack standup-channel message stream
This is what we'd see for your team.
Connect GitHub, Slack, Linear, Notion, and Google. We mine the actual behavioural patterns and ship a weekly briefing your VPE will actually read.
Book a demo →FIG 6 · Embed in your README
Paste this in your README. The badge updates daily and links back to this Mirror.
[](https://www.assemblr.net/mirror/kubernetes)