---
title: The Node OS Is Part of Your Platform Contract
weight: 4
tags:
 - platformengineeringday
 - keynote
 - sponsor
 - vmware
---

<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
<!-- {{% button href="https://docs.google.com/presentation/d/1nEK0CVC_yQgIDqwsdh-PRihB6dc9RyT-" style="tip" icon="person-chalkboard" %}}Slides{{% /button %}} -->
<!-- {{% button href="https://colocatedeventseu2026.sched.com/event/2DY6g" style="error" icon="calendar" %}}Sched Link{{% /button %}} -->
<!-- {{% button href="https://github.com/graz-dev/automatic-reosurce-optimization-loop" style="info" icon="code" %}}Code/Demo{{% /button %}}  -->
<!-- {{% button href="https://cloudnativeplatforms.com" style="info" icon="link" %}}Website/Homepage{{% /button %}}  -->

The usual "teaser" ment to get people to visit their stand and other talks

## 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