Helm 4: A Decade On, Built for Modern Kubernetes

Welcome back to your newsletter!

Helm has reached its tenth anniversary with the release of Helm 4, a major update designed to modernise how engineering teams build, package, and deploy applications on Kubernetes.

While the core interface remains familiar, the upgrade brings meaningful improvements in developer experience, plugin architecture, chart evolution, and long-term maintainability.

Helm was originally created to simplify application delivery on Kubernetes. A decade later, Helm 4 stays true to that goal but removes legacy constraints that held back performance and extensibility.

Let`s dive in.

A more capable SDK for teams building on Helm

For platform teams and internal tooling engineers, Helm 4 delivers a significantly improved Software Development Kit (SDK):

• Modern Go logging – adopts current Go logging patterns, making logs more consistent and enabling teams to plug in their preferred loggers.
• Embeddable commands – Helm commands can now be embedded directly inside other applications, allowing teams to build richer internal tooling.
• Support for modern Kubernetes – including server-side apply, ensuring Helm aligns with how today’s clusters operate.

This upgrade makes Helm far easier to integrate into CI/CD systems, internal developer platforms, and custom automation.

A new plugin system built for portability

Helm 4 introduces a redesigned plugin system that is both more powerful and more flexible:

• WASM-based plugins – Plugins can now be written in WebAssembly, running consistently across operating systems and architectures.
• Traditional plugins still work – Existing plugins continue to function, protecting current workflows and investments.

This allows teams to expand Helm without worrying about compatibility issues across environments.

A future-ready foundation for charts

One of the biggest shifts in Helm 4 is how it handles chart evolution:

• Groundwork for new chart features – Helm 4 introduces a framework that lets chart authors adopt substantial changes safely.
• Breaking changes without breaking users – New capabilities can be added in ways that avoid disruption for existing deployments.

This makes it easier for organisations to maintain chart libraries that scale with their infrastructure.

A message from Helm’s creators

“We started Helm to make deploying applications on Kubernetes easier for developers and operators alike. A decade later, it’s incredible to see Helm continue to solve that same core problem—now with greater reach, scale, and community support than we ever imagined.” — Matt Butcher, co-creator of Helm

Why it matters to you

For CTOs and Heads of Engineering, Helm 4 signals a maturing ecosystem where stability and extensibility matter as much as speed:

• Upgrades are non-disruptive.
• Plugins become easier to build and maintain.
• SDK improvements reduce friction in platform engineering.
• Chart evolution becomes safer and more predictable.

As Kubernetes celebrates its own ten-year milestone, Helm 4 is a timely foundation for the next phase of cloud-native growth.

Is your team hiring?

We work with global businesses across the UK, Germany and the US to help them find top talent quickly.

Reach out to us for a recruitment strategy session

🔥 Hot Jobs by develop 🔥

Software Engineer - Mansfield

Lead Python Engineer - Spain

Head of Product (Gaming) - Berlin

Software Engineer - Newcastle

😎 Our Social Stories

How To Avoid The Too Many Cooks Syndrome In Digital Change

Security-aware and cloud native full stack devs

Are you following us?

Click here to be the first to get our updates!