BEGIN:VCALENDAR
VERSION:2.0
PRODID:IEEE vTools.Events//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/Indiana/Indianapolis
BEGIN:DAYLIGHT
DTSTART:20260308T030000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251102T010000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20251206T014834Z
UID:8BE7A113-EC48-463D-A2E2-EC6472BDF0B1
DTSTART;TZID=America/Indiana/Indianapolis:20251205T183000
DTEND;TZID=America/Indiana/Indianapolis:20251205T203000
DESCRIPTION:Brant together with Sidero Labs Head of Developer Relations\, J
 usin Garrison\, will talk about Kubernetes and container orchestration out
 side of the big cloud providers. In particular\, Brant will talk about dec
 isions his company has made and still have to make in hosting Kubernetes w
 orkloads locally.\n\nSpeaker(s): Justin\, Brant\n\nAgenda: \nJustin: What&#39;
 s Talos and Omni and their relationship to each other and to Kubernetes?\n
 Brant: In practice/example: How we set up our clusters and automated their
  setup and maintenance.\nBrant: Gaps we still have to figure out and what&#39;
 s been tried or researched.\n- Log aggregation\n- Security monitoring\n- S
 torage\n- Service exposure\nJustin: Places where Talos/Omni plans might se
 rve us such as the managed control plane plan. Alternate choices for what 
 we&#39;ve done.\nQ&amp;A if any\n\nVirtual: https://events.vtools.ieee.org/m/51567
 3
LOCATION:Virtual: https://events.vtools.ieee.org/m/515673
ORGANIZER:brant@gurganus.name
SEQUENCE:19
SUMMARY:Kubernetes with Omni and Talos
URL;VALUE=URI:https://events.vtools.ieee.org/m/515673
X-ALT-DESC:Description: &lt;br /&gt;&lt;p&gt;Brant together with Sidero Labs Head of De
 veloper Relations\, Jusin Garrison\, will talk about Kubernetes and contai
 ner orchestration outside of the big cloud providers. In particular\, Bran
 t will talk about decisions his company has made and still have to make in
  hosting Kubernetes workloads locally.&lt;/p&gt;&lt;br /&gt;&lt;br /&gt;Agenda: &lt;br /&gt;&lt;div&gt;J
 ustin: What&#39;s Talos and Omni and their relationship to each other and to K
 ubernetes?&lt;/div&gt;\n&lt;div&gt;Brant: In practice/example: How we set up our clust
 ers and automated their setup and maintenance.&lt;/div&gt;\n&lt;div&gt;Brant: Gaps we 
 still have to figure out and what&#39;s been tried or researched.&lt;/div&gt;\n&lt;div&gt;
 &amp;nbsp\;- Log aggregation&lt;/div&gt;\n&lt;div&gt;&amp;nbsp\;- Security monitoring&lt;/div&gt;\n&lt;
 div&gt;&amp;nbsp\;- Storage&lt;/div&gt;\n&lt;div&gt;&amp;nbsp\;- Service exposure&lt;/div&gt;\n&lt;div&gt;Jus
 tin: Places where Talos/Omni plans might serve us such as the managed cont
 rol plane plan. Alternate choices for what we&#39;ve done.&lt;/div&gt;\n&lt;div&gt;Q&amp;amp\;
 A if any&lt;/div&gt;
END:VEVENT
END:VCALENDAR

