<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vmware :: Tag :: Rejekts2026 and KubeCon EU 2026</title>
    <link>https://kubecon25.nicolai-ort.com/tags/vmware/index.html</link>
    <description></description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://kubecon25.nicolai-ort.com/tags/vmware/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Node OS Is Part of Your Platform Contract</title>
      <link>https://kubecon25.nicolai-ort.com/day0/04_vmware/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://kubecon25.nicolai-ort.com/day0/04_vmware/index.html</guid>
      <description>The usual “teaser” ment to get people to visit their stand and other talks&#xA;What happens if A kernel update breaks the CNI and affect every pod by breaking An app mutates the system MTU breaking all other networking operations and even cluster management Baseline Platform engineers build abstractions every day Infra owns the hardware and hypervisor Platform own kubnernetes, gitops and so on Problem: Who owns the Node OS Node states ClusterAPI assumes immutable nodes by relacing them when updating the os, kubernetes or cri But we want mutability for: Simple config updates, Zertificate things So why immutable: Version alignment, drift detection</description>
    </item>
    <item>
      <title>Rebuilding our platforms in the age of ai</title>
      <link>https://kubecon25.nicolai-ort.com/day0/06_aiplatforms/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://kubecon25.nicolai-ort.com/day0/06_aiplatforms/index.html</guid>
      <description>A call to joint them at their booth and reading their whitepaper.&#xA;BAseline 2024: LLMs 2025: Agents 2026: Our platform/infra can not keep up -&gt; The number of def Mandate Drive AI-readyness initiatives Data-driven ai rollout Measure for impact instead of activity or speed Paved paths and guardrails AI infra optimizations Observations Whats good for humans is also good for llms (clear documentation, strucutred data, readable code, …) Metrics from out tools only measure that something is happening -&gt; We need a framwork for DX and AI</description>
    </item>
  </channel>
</rss>