Kubernetes package manager Helm has reached a new milestone with the release of Helm 3, according to the Cloud Native Computing Foundation.
Helm 3 officially removes Tiller, which was introduced in the Helm 2 development cycle. Tiller made it possible for different operators to interact with the same set of releases, Helm explained. The team realized, however, that Tiller’s main goal could actually be accomplished without Tiller.
By removing Tiller, the security model for Helm will be simpler. According to the team, Helm 3 supports modern security, identity, and authorization features of modern Kubernetes.
Information about a release used to be stored in Tiller, but with that gone, release information will now be stored in the same namespace as the release.
It also improved the Helm upgrade strategy by allowing three-way strategic merge patches. In version 2, it used a two-way merge patch where it compared the most recent chart’s manifest with the proposed chart’s manifest. Now it will compare the old manifest, its live state, and the new manifest.
Other changes are that Secrets are now the default storage driver, Go import path has been changed, the capabilities built-in object has been simplified, JSON Schemas can now be used to validate chart values, and more. A detailed list of features can be found here.