BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2025//speaker//3PBDWP
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-cz-2025-JU97MG@pretalx.devconf.info
DTSTART;TZID=CET:20250612T144500
DTEND;TZID=CET:20250612T152000
DESCRIPTION:Imagine this: you train your AI model\, spend a lot of time and
  resources\, feed it internal data. When you are finally done with it\, yo
 u containerize it and deploy it to a Kubernetes cluster. Everything's fine
 . Until it isn't! Another tenant you are sharing the cluster with somehow 
 managed to get a hold of your image. How could it be? They cannot access a
 ny of your namespaces\, you made sure of that.\n\nThis session will introd
 uce you to the trouble of multi-tenancy of images you pull with Kubernetes
 \, and you will learn about a new (alpha) feature that aims to finally sol
 ve multi-tenant access to Kubernetes node's images.
DTSTAMP:20260911T012007Z
LOCATION:E112 (capacity 156)
SUMMARY:Kubernetes Multitenancy in Image Pulling - Standa Láznička
URL:https://pretalx.devconf.info/devconf-cz-2025/talk/JU97MG/
END:VEVENT
END:VCALENDAR