Aflevering 141: Helm 4 - Plugins, OCI and Why Nothing Broke

Andrew "Andy" Block writes books and reviews pull requests at thirty thousand feet over the Pacific, because as he says, he can sleep when he's dead. Between Red Hat's services organization and four talks at KubeCon Amsterdam, he sat down with Ronald Kers and Jan Stomphorst to talk about the first major Helm release in almost five years.

Helm 4 is a story about restraint. Helm has become load bearing for an enormous number of enterprises, and a strict versioning policy left technical debt with nowhere to go. Helm 4 clears that debt without breaking anyone. Replace the binary, keep your charts, notice almost nothing. After what the Tiller removal in Helm 3 cost teams like Jan's, that is the achievement.

Underneath sits more than the version number suggests: a Wasm based plugin model that finally makes Helm properly extensible, a serious API and logging cleanup, and better status handling built on libraries contributed out of the Flux community. Charts v3 comes next, letting you swap Go templating for Jinja or Rust, and opening the door to downloader and signer plugins.

That plugin model matters most for signing. Andy asked a room of roughly three hundred people how many sign their Helm charts. Three hands went up. GPG is painful enough that even a security specialist avoids it, so Sigstore behind a plugin becomes the realistic path to provenance. On the OCI side, per repository credentials and transparent mirroring mean organizations can stop forking charts just to repoint them internally.

The conversation widens from there: why Kustomize and Helm complement rather than compete, why European organizations are moving back on prem, and whether AI now produces code faster than any maintainer can honestly review it.

Andy's crystal ball isn't about features at all. It's about approachability, and lowering the barrier for the newcomers who made up well over half the room at KubeCon.

‍