Aflevering 132: From CPU to GPU: The New Reality of Kubernetes 1.36

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.

Instead of reacting to vulnerabilities after they appear, the conversation explores a different mindset. One where security isn’t something you bolt on later, but something you start with. Not “shift left”… but start left.

Veel organisaties draaien al vijf jaar Kubernetes, maar hebben vaak nog maar 5–10% van hun applicatielandschap gemoderniseerd . Volgens Jan ligt het echte probleem niet bij het platform, maar bij legacy-applicaties en de businesscontext eromheen.

Too often, PAM is treated as a compliance checkbox. Something you buy because an auditor, insurer, or regulation tells you to. Maurice explains why that mindset is dangerous

Kubernetes and container technologies play a key enabling role by providing consistent environments, repeatable deployments, version control, and zero-downtime upgrades for customers running ERP and custom software solutions.

Chris shares his journey from traditional telco and enterprise networking, through VMware NSX, to modern cloud and Kubernetes platforms. The conversation dives deep into why networking often becomes more complex—not less

Jussi introduces k0s, a fully upstream Kubernetes distribution packaged as a single, statically compiled binary with zero dependencies.

Een van de eerste onderwerpen is Image Max Age, een nieuwe kubelet-optie waarmee je expliciet kunt bepalen hoe lang ongebruikte container images op nodes blijven staan.