BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-us-2026//talk//3DBTDH
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-3DBTDH@pretalx.devconf.info
DTSTART;TZID=EST:20260924T134000
DTEND;TZID=EST:20260924T141500
DESCRIPTION:Shipping a solution made of several Helm-based products (platfo
 rm add-ons\, operators\, integrations) usually means bespoke glue code\, f
 ragile ordering\, and configs that fall apart between a demo cluster and p
 roduction. Helmet is a reusable Kubernetes installer framework that treats
  dependency topology\, integration wiring\, and configuration as first-cla
 ss concerns so teams can focus on their charts—not one-off installers.\n
 \nThis session introduces Helmet’s core ideas: chart annotations that dr
 ive install order and namespace placement\, integration secrets coupled to
  products via declarative rules\, embedded installer bundles\, and CLI/MCP
  workflows that stay consistent from first deploy onward. We will walk thr
 ough how the same artifact and patterns support a quick demo\, a PoC on a 
 shared cluster\, and a production rollout—where the main differences are
  configuration depth and operational gates\, not a rewrite of your install
 er.\n\nYou will leave with a mental model of when Helmet fits\, how multi-
 product composition works in practice\, and what to plan for as you harden
  from demo to production (validation\, topology inspection\, integration l
 ifecycle).\n\nAudience / level: Platform engineers\, Kubernetes admins\, a
 nd teams shipping internal platforms or ISV-style installers\; intermediat
 e Kubernetes + Helm familiarity assumed.\n\nTakeaways:\n\n- How Helmet res
 olves deployment order and integration dependencies from chart metadata.\n
 - How one installer can evolve from demo → PoC → production through co
 nfig and process\, not new code each time.\n- Where extensions (integratio
 ns\, templating\, automation/MCP) fit in the lifecycle.\n- How you can end
  up with a production ready gitops repo for day two operation.
DTSTAMP:20260727T174741Z
LOCATION:101 (Capacity 48)
SUMMARY:Helmet: Composing Multi-Product Kubernetes Installers Without Losin
 g Your Mind - David Peraza\, Romain Arnaud
URL:https://pretalx.devconf.info/devconf-us-2026/talk/3DBTDH/
END:VEVENT
END:VCALENDAR