Whats in with Helm v3? Quick look — OpsInsights

Jothimani Radhakrishnan's photo
Jothimani Radhakrishnan
·Nov 10, 2019·

2 min read

Hello readers, in our last blog we have went through using helm charts, which includes basic usage. Now lets see whats new in the latest version of helm charts v3 which has more stable version of its beta.

No more Tiller ! Lua templates are going to be introduced alongside Go templates

  • Requirements are now listed in the Chart.yaml file instead of the requirements.yaml file.

  • A crd directory has been added to charts for the placement of CRDs. These will be installed before the rendering of the templates is performed. Once the Kubernetes community has worked out more workflow details with CRDs more features can be added to Helm to support them.

  • The crd-install hook has been removed and will not work for Helm v2 charts. A “legacy” plugin will be released by the Helm project to support v1 charts with thecrd-install hook.

  • Experimental feature gates are now supported. As new potential features are added to Helm they can be worked on as experiments and enabled using an environment variable.

  • Pushing and pulling charts from OCI registries is now an experimental feature. The final details of this feature are being worked out with the OCI on the proper use of the API. To access this feature set the environment variable HELM_EXPERIMENTAL_OCI=1 needs to be set.

  • helm server has been removed.

  • Helm now supports library charts. These charts are not meant to be installed but can be depended on and referenced by other charts. These were inspired by the common chart in the incubator repository.

  • helm test received some major refactoring. This included the test-success hook’s behavior coming in line with other hooks and the removal of the test-failure hook due to lack of use.

  • Several CLI changes have happened for usability including:

  • helm inspect is now helm show

  • helm fetch is now helm pull

  • helm delete is now helm uninstall

  • Instead of using the --purge flag on helm uninstall the behavior is to use the --keep-history if you want to keep the history.

Will soon write another blog to how to upgrade from helm V2 to V3 without damaging our resources.

Originally published at https://opsinsights.dev on November 10, 2019.

Did you find this article valuable?

Support Jothimani Radhakrishnan by becoming a sponsor. Any amount is appreciated!

Learn more about Hashnode Sponsors
 
Share this