BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//bbuzz22//speaker//V8DN3L
BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:DAYLIGHT
DTSTART:20210613T000000
TZNAME:CEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20211031T030000
RDATE:20221030T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20220327T030000
RDATE:20230326T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:What we learned from reading 100+ Kubernetes Post-Mortems - Noaa B
 arki
DTSTART;TZID=Europe/Berlin:20220613T140000
DTEND;TZID=Europe/Berlin:20220613T144000
DTSTAMP:20261009T201935Z
UID:pretalx-bbuzz22-LUBLXC@pretalx.com
DESCRIPTION:When building our Kubernetes-native product\, we wanted to fin
 d the most common sources of failures\, anti-patterns and root causes for 
 Kubernetes outages\, so we got to work. We rolled up our sleeves and read 
 100+ Kubernetes post-mortems. This is what we discovered.\n\nA smart perso
 n learns from their own mistakes\, but a truly wise person learns from the
  mistakes of others.\n\nWhen launching our product\, we wanted to learn as
  much as possible about typical pains in our ecosystem\, and did so by rev
 iewing many post-mortems (100+!) to discover the recurring patterns\, anti
 -patterns\, and root causes of typical outages in Kubernetes-based systems
 .\n\nIn this talk we have aggregated for you the insights we gathered\, an
 d in particular will review the most obvious DON’Ts and some less obviou
 s ones\, that may help you prevent your next production outage by learning
  from others’ real world (horror) stories.
LOCATION:Kesselhaus
URL:https://pretalx.com/bbuzz22/talk/LUBLXC/
END:VEVENT
END:VCALENDAR