Aflevering 139: Waarom een Kubernetes-cluster zichzelf niet moet beheren

Kubernetes-platformen worden uitgerold en beheerd over virtualisatielagen, bare metal en de cloud heen. Eric heeft een lange geschiedenis die teruggaat tot de vroege vCenter-tijd, via de opkomst van container orchestration (Mesos, Docker Swarm)

In their KubeCon talk "No Shame in Just Paying," they shared how they tackled this consolidation project: migrating all workloads to three standardized, fully managed Kubernetes distributions.

DB tune focuses entirely on Postgres and deploys a narrow, production-safe AI agent that reads performance metrics and iteratively adjusts server parameters (GUCs) until the system converges on an optimal configuration.

vLLM serves as a "Rosetta Stone" between the ever-growing zoo of models (Llama, DeepSeek, Mistral, Qwen, Nvidia Nemotron) and accelerators (Nvidia, AMD, Intel, Google TPUs).

Mohamed and Thierry discuss why OpenStack is still highly relevant at massive scale, especially for organizations requiring multi-tenancy, hardware abstraction, GPU enablement, HPC workloads, and advanced networking performance.

Carl shares how edge computing has matured. What used to require explaining the concept itself has now shifted toward real-world adoption, with use cases across retail, manufacturing, telecom and beyond.

A key topic in this episode is Kube Solo, a lightweight Kubernetes distribution that can run on roughly 200 MB of RAM. The goal is to make Kubernetes usable in environments where traditional clusters are too heavy, such as IoT and Edge.

Many of the changes in this release focus on closing gaps and improving control, such as more fine-grained authorization, better admission control during node startup, and addressing previously existing vulnerabilities.

A key theme is balance: developers need freedom, but within secure guardrails. That’s why pipelines are not immediately blocked on vulnerabilities, but first used to provide visibility and gradually increase maturity.