~/talk

AI as a Platform Engineer: Explaining Kubernetes Failures, Not Just Detecting Them

links:none on file
slides:none on file

Comcast describes an AI explanation layer that cuts Kubernetes deployment troubleshooting from 30–45 minutes to about 5 by combining declarative JSON rules (failure domains, ownership, signal lists) with LLM summarization at temperature 0, PII scrubbing, and structured four-field output (responsible party, classification, root cause, remediation) written back into the custom resource status. It runs in two modes (automatic on failures and operator-invoked), handles multi-region private clouds and ~400 clusters with 30+ add‑ons, and averages 8k–16k tokens per request.

AI-written summary · about

  1. 0:00Platform engineering and AI
  2. 3:11Why platforms exist
  3. 8:50AI explains Kubernetes failures
  4. 12:21Building AI explanation layers
  5. 21:25AI for day two operations
  6. 23:52AI for platform onboarding
  7. 28:50Evaluating AI agent performance
  8. 31:50Platform vs application failures
  9. 37:50Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.