BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-us-2026//speaker//WPHZWM
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:20260727T165130Z
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
BEGIN:VEVENT
UID:pretalx-devconf-us-2026-XWZLYQ@pretalx.devconf.info
DTSTART;TZID=EST:20260925T123000
DTEND;TZID=EST:20260925T135000
DESCRIPTION:In this workshop you will assemble a small but realistic soluti
 on from a few products and integrations using the Helmet framework—not b
 y writing a custom orchestrator from scratch\, but by composing charts\, w
 iring integrations\, and driving configuration the way Helmet expects.\n\n
 We start from an embedded installer layout: charts on disk\, a blueprint t
 hat declares what is in the bundle\, and merged configuration for settings
 \, products\, and integrations. In guided exercises you will add or adjust
  pieces\, run topology to see resolved order\, exercise config workflows (
 including dry-run)\, and connect integration metadata to consuming charts.
  By the end\, you will have walked the path from “empty bundle” to “
 coherent multi-chart story” with clear seams for swapping demo vs produc
 tion values.\n\nPrerequisites: Laptop with kubectl and cluster access (or 
 local Kubernetes) as announced by organizers\; Helm basics\; comfortable e
 diting YAML. No prior Helmet experience required.\n\nFormat note: Hands-on
 \, goal-oriented steps with helper repos or embedded examples\; instructor
 s troubleshoot common Helm/topology mistakes.\n\nTakeaways:\n\n- Scaffold 
 or extend an installer that combines multiple Helm charts under one CLI.\n
 - Express dependencies and integrations so installs stay reproducible.\n- 
 Practice the demo → tighter PoC leap using the same composition model.
DTSTAMP:20260727T165130Z
LOCATION:107 (Capacity 20)
SUMMARY:Build a Multi-Product Kubernetes Solution with Helmet (Hands-On) - 
 David Peraza\, Romain Arnaud
URL:https://pretalx.devconf.info/devconf-us-2026/talk/XWZLYQ/
END:VEVENT
END:VCALENDAR
