BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.cloud-native.rejekts.io//cloud-native-rejekts-na-sal
 t-lake-city-2024//TXQ7UR
BEGIN:VTIMEZONE
TZID:MST
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1
TZNAME:MST
TZOFFSETFROM:-0700
TZOFFSETTO:-0700
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-cloud-native-rejekts-na-salt-lake-city-2024-AXVESD@cfp.cloud-na
 tive.rejekts.io
DTSTART;TZID=MST:20241111T154500
DTEND;TZID=MST:20241111T161500
DESCRIPTION:One of the super powers Kubernetes gives us is our ability to e
 xpand the API\, modeling our architectures and dependencies with CRDs\, le
 veraging Kubernetes as a platform for building platforms. Getting somethin
 g up and running can take just minutes\, but debugging synchronization pro
 blems and unexpected behaviors can take days or weeks for folks just start
 ing out. Compound this problem with a lack of advanced controller creation
  advice\, and a lack of direction on the norms and expectations around spe
 c/status and behavior\, and it is easy to see how even hardened engineers 
 with years of experience can fail on their first attempts at writing their
  first Kubernetes based declarative API.\n\nWe cover will some common mist
 akes and mis-understandings around reconciliation\, and explain what we ca
 n do instead. And look at unspoken norms around API shapes in spec and sta
 tus\, explain why they are useful\, and send you on your way with new foun
 d confidence to wield the power of a platform developer.
DTSTAMP:20261007T155218Z
LOCATION:Theater
SUMMARY:The wrong way to Reconcile - Scott Nichols
URL:https://cfp.cloud-native.rejekts.io/cloud-native-rejekts-na-salt-lake-c
 ity-2024/talk/AXVESD/
END:VEVENT
END:VCALENDAR