BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2026//talk//W7KJKA
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-2026-W7KJKA@pretalx.devconf.info
DTSTART;TZID=CET:20260618T133500
DTEND;TZID=CET:20260618T135000
DESCRIPTION:kubectl is great for the basics\, but it starts to feel clunky 
 once you’re managing complex\, stateful stacks. If you’ve ever had to 
 exec into a "toolbox" pod just to run a simple Ceph health check or hunt t
 hrough nested CRDs while an alert is firing\, you know the frustration. It
 ’s a high-friction workflow that kills productivity.\n\nIn this session\
 , we’ll look at how Krew fixes this by turning kubectl into a modular po
 werhouse. I’ll explain the mechanics of how Krew plugins actually work
 —leveraging binary naming conventions to create a native-feeling CLI exp
 erience. Using kubectl-rook-ceph as our primary example\, we’ll demonstr
 ate how to collapse complex storage operations into simple\, actionable on
 e-liners. You’ll see how this plugin abstracts away the "scary" parts of
  Rook-Ceph\, like OSD maintenance and recovery\, directly from your local 
 terminal. Leave the "pod-hopping" behind and learn how to build a CLI that
  actually understands your stack.
DTSTAMP:20260430T125647Z
LOCATION:A113 (capacity 64)
SUMMARY:Beyond the Defaults: Extending Kubectl with Krew - Subham Rai\, Nik
 hil Ladha
URL:https://pretalx.devconf.info/devconf-cz-2026/talk/W7KJKA/
END:VEVENT
END:VCALENDAR