BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.cfgmgmtcamp.org//2020//QNEFHU
BEGIN:VTIMEZONE
TZID:Europe/Brussels
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-2020-BJYDHK@cfp.cfgmgmtcamp.org
DTSTART;TZID=Europe/Brussels:20200204T124000
DTEND;TZID=Europe/Brussels:20200204T124500
DESCRIPTION:cri-o is considered safer than Docker lacking the latter’s pr
 ivileged central daemon and\, additionally\, produces less overhead becaus
 e it does not contain techniques already provided by\, for instance\, kube
 rnetes clusters. That’s why it is gaining popularity as an alternative t
 o Docker. The large distributions already switched to cri-o as a default b
 ackend in their container plattforms (OpenShift and CaaS). But I\, persona
 lly\, had to overcome a lot of uncertainties before actually starting to u
 se it.\nThere were many open questions regarding the effort needed for a s
 uccessful transition\, change of habits or procedures:\n- Is the transitio
 n irreversible?\n- Where do I get images from? Are the runtimes compatible
 ?\n- Which new commands do I have to learn?\n- Can I continue using my CI/
 CD system?\n- Do I have to change my workflow?\n\nSimilar question arose i
 n my work environment\, so I started to collect these questions – and th
 e answers.
DTSTAMP:20260718T085226Z
LOCATION:D Aud
SUMMARY:Switching from Docker to CRI-O - Jan Bundesmann
URL:https://cfp.cfgmgmtcamp.org/2020/talk/BJYDHK/
END:VEVENT
END:VCALENDAR