BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-us-2026//talk//SYX3QX
BEGIN:VTIMEZONE
TZID:EST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T070000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T080000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-us-2026-SYX3QX@pretalx.devconf.info
DTSTART;TZID=EST:20260925T131000
DTEND;TZID=EST:20260925T134500
DESCRIPTION:In the inception of Kubernetes\, a core design philosophy was P
 ods are "cattle" rather than "pets" where they can be easily replaced and 
 replicated. As Kubernetes has dominated the world of computing\, that desi
 gn philosophy continually grows fuzzier. Today\, application designers hav
 e many pet Pods that are difficult to schedule\, start\, and run\, and the
 y'd take the suggestion to "move" rather than tear down and replace.\n\nIn
  the Kubernetes Checkpoint/Restore working group\, we're looking to canoni
 cally solve this problem. There has already been rudimentary checkpointing
  support\, but we're looking to do more. Join Peter Hunt as they walk thro
 ugh what the WG has been working on\, and learn about the state of the art
  of process migration at enterprise scale. And yes\, it can be used for AI
  applications too.
DTSTAMP:20260727T174809Z
LOCATION:101 (Capacity 48)
SUMMARY:We Should Take Our Pods and Push Them Somewhere Else: Checkpoint/Re
 store in Kubernetes - Peter Hunt
URL:https://pretalx.devconf.info/devconf-us-2026/talk/SYX3QX/
END:VEVENT
END:VCALENDAR