Helm 4: What’s New in the Open Source Kubernetes Package Manager?

Key Concepts

• Helm: A package manager for Kubernetes.
• CNCF (Cloud Native Computing Foundation): A neutral home for collaboration on cloud-native technologies.
• Kubernetes: An open-source system for automating deployment, scaling, and management of containerized applications.
• WebAssembly (Wasm): A binary instruction format for a stack-based virtual machine, designed as a portable compilation target for programming languages.
• Spin: An open-source project for building serverless functions using WebAssembly.
• Fermion: A company building cloud computing solutions using WebAssembly.
• SUSA: A technology company providing enterprise Linux distributions, Kubernetes management (Rancher), and cloud-native solutions.
• Chart: A Helm package containing pre-configured Kubernetes resources.
• Plugins: Extensible components for Helm.
• GitOps: An operational framework that uses Git as the single source of truth for declarative infrastructure and applications.
• Rancher: A Kubernetes management platform.
• Liz (AI Assistant): An AI assistant integrated into Rancher for navigating Kubernetes.

Helm: A Decade of Evolution and the Launch of Helm 4

This section details the origin, evolution, and recent advancements of Helm, a critical package manager for Kubernetes.

Genesis of Helm

Helm's journey began in October 2015 as a hackathon project at Deis, a company developing an open-source alternative to Heroku. The initial project, named "Kate's Place," was conceived as the "npm of the Kubernetes world" to address the emerging need for package management in the nascent Kubernetes ecosystem. The hackathon team, motivated by a $75 gift card, developed a functional package manager. The project's potential was recognized by Deis's CEO and CTO, who encouraged its development. A subsequent renaming effort, driven by a preference for a nautical theme, led to the adoption of the name "Helm."

Evolution and Graduation within CNCF

Helm's development mirrored the growth of Kubernetes and the Cloud Native Computing Foundation (CNCF). It transitioned from being a sub-project of Kubernetes to becoming an independent project under the CNCF. Helm achieved "graduated" status within the CNCF, signifying its maturity and widespread adoption, being one of the earliest projects to do so. This evolution involved significant milestones like Helm 1, Helm 2, and the long-standing Helm 3.

Helm 4: Key Features and Modernization

Helm 4, launched at CubeCon + CloudNativeCon North America, represents a significant update, addressing technical debt and introducing modern capabilities.

• WebAssembly (Wasm) Based Plugins: A major highlight of Helm 4 is the introduction of Wasm-based plugins. This move away from file-system execution offers enhanced portability across various operating systems (Linux, macOS, Windows) and architectures (ARM, Intel, and multiple Linux architectures). This aligns with the growing popularity of WebAssembly as a plug-in architecture.
• API Modernization and Logging: The logging system within Helm has been significantly modernized. Leveraging SLog, Helm now integrates more cleanly with various application logging libraries. This is crucial as Helm is not only a client but also a Software Development Kit (SDK) used by other projects like Flux, Argo, and internal SUSA systems.
• Chart Architecture Rearchitecture: The internal architecture for Helm charts (packages) has been re-architected to accommodate evolving Kubernetes practices and to enable future enhancements. This foundational change is expected to pave the way for new features in subsequent minor releases (e.g., 4.1, 4.2) related to chart management and installation control.
• Reproducible Chart Builds: A highly anticipated feature that received enthusiastic reception is reproducible chart builds. This ensures that packaging a chart multiple times will result in the same SHA and digest, enhancing reliability and predictability.
• Color in Output: A seemingly simple, yet popular, feature is the addition of color to Helm's output, improving readability and user experience.

Addressing Criticisms and Core Philosophy

Helm has faced criticisms regarding user-friendliness and default security settings. The Helm team's approach is to focus on enabling the "80%" of users, particularly those who may not be deeply embedded in the complexities of the cloud-native ecosystem.

• Focus on the Majority: Helm prioritizes making the core package management functionality accessible and successful for a broad user base, rather than catering to every niche requirement of advanced users.
• Extensibility: The new plug-in system in Helm 4 is designed to empower users to extend Helm's capabilities when necessary, whether for open-source sharing or internal organizational use.
• Core Principle: Package Manager: A guiding principle for Helm has been to remain focused on its core function as a package manager for Kubernetes. This deliberate focus prevents feature bloat and allows other projects to excel in complementary areas like configuration management.
• Learning from Mistakes: The team acknowledges past missteps, such as the gratuitous client-server division in Helm 2, and has learned to prioritize core functionality and avoid overreach.

Future Outlook: Helm 4.x and Beyond

The architecture changes in Helm 4 are designed to be enablers for future development.

• New Chart Format (API Version 3): Within months, Helm will introduce API Version 3 for charts, starting as an experiment. This allows for iterative development and feedback before a wider release.
• Release Process Improvements: Helm will begin signing releases with Cosign, moving beyond PGP signing.
• Helm 5 (Long-Term Vision): While years away, future iterations like Helm 5 are envisioned to focus on "boring infrastructure" enhancements that can benefit other projects, such as those in the GitOps space.

Company Updates

Fermion Technologies

Fermion has experienced a significant period of growth and innovation.

• Spin in CNCF: The open-source project Spin, for building serverless functions with WebAssembly, has been accepted into the CNCF as a sandbox project.
• Project Pavilion: Fermion had its first project pavilion at CubeCon, a significant milestone for community engagement.
• New Spin Release: A recent release of Spin introduces support for WebAssembly 3.0 and Wazi P3, keeping it at the forefront of WebAssembly evolution.
• Fermion Wasm Functions (GA): The enterprise product, Fermion Wasm Functions, initially launched on Okamaya as an edge-based solution in two regions, has now expanded to 24 regions globally. It is capable of handling tens of millions of simultaneous requests and has achieved General Availability (GA) with uptime guarantees and global support.

SUSA

SUSA has integrated AI into its cloud-native offerings.

• AI in Rancher: SUSA has added AI capabilities to Rancher, its Kubernetes management platform.
• Liz (AI Assistant): An AI assistant named "Liz" (short for lizard, referencing the SUSA chameleon) has been introduced. Liz helps users navigate Kubernetes clusters, simplifies management, and provides insights without requiring deep technical knowledge. This aims to make the complexity of cloud-native environments more accessible.

This summary provides a detailed overview of the discussion on Helm's past, present, and future, alongside updates from Fermion and SUSA, all within the context of the CubeCon + CloudNativeCon North America event.