Once a Zenko instance is up and running, you can upgrade it with a simple Helm command.

Before Upgrade

Most installations use custom values to set them up as required. Compare any live values to those to be applied in an upgrade to ensure consistency and prevent undesired changes.

To see the custom values of a running Zenko instance:

$ helm get values {{zenko-release-name}} > pre_upgrade_values.yaml


Values added at upgrade override and completely replace the values used to configure the running instance. Before invoking helm upgrade, carefully review all changes between the values used in the running instance against the values you intend to push in the upgrade.

In a production environment, it is a best practice to run an upgrade simulation. For example:

$ helm upgrade zenko ./zenko --dry-run --debug


A production environment may neccessitate additional validation before upgrading. Upgrades run with the --dry-run flag simulate and, if possible, validate a compatible upgrade. If the --debug flag is set, Helm outputs all templated values and deployment configurations to be installed. These are basic validations, but their upgrade implications must be considered by both the Zenko and Kubernetes administrators.


To upgrade Zenko:

  1. Back up your existing Zenko directory.

    $ cp -r Zenko Zenko-backup
  2. Download the latest stable version (.zip or .tar.gz) from https://github.com/scality/Zenko/releases

  3. Unpack the .zip or .tar.gz file and navigate to Zenko/kubernetes/.

  4. Copy Zenko/kubernetes/options.yaml from your existing Zenko source directory to the same directory in the new Zenko source.

  5. If you have modified the node count from the default value of 3, go to Zenko/kubernetes/zenko/values.yaml in the new Zenko source and edit the nodeCount value to match the existing nodeCount value.

  6. From the kubernetes/ directory of the new Zenko source, enter this Helm command, inserting your Zenko server’s name:

    $ helm upgrade {{zenko-server-name}} ./zenko

    If you are using custom values, reuse options.yaml on upgrades.

    $ helm upgrade {{zenko-server-name}} ./zenko -f options.yaml
  7. On success, Helm reports:

    Release "{{zenko-server-name}}" has been upgraded. Happy Helming!

    After a few seconds, Helm displays a voluminous status report on the server’s current operating condition.


    Expect the cluster to take a few minutes to stabilize. You may see CrashLoopBackoff errors. This is normal, expected behavior.

With the introduction of Helm 3, Helm 2 charts are still supported. Helm 3 charts introduce improved functionality, and support existing Helm 2 charts and in-place upgrades and conversion.

To upgrade existing Helm 2 charts to Helm 3, install the 2to3 plugin and use the following steps to migrate and clean up your Helm 2 configuration, releases, and Tiller deployment.
  1. Install the 2to3 plugin for Helm 3.
$ helm3 plugin install https://github.com/helm/helm-2to3
  1. Update the existing Helm 2 configuration. Always test with the --dry-run option before migrating or updating a production system.
$ helm3 2to3 move config --dry-run
$ helm3 2to3 move config
  1. After Helm 3 configuration is complete, convert the existing deployment with the following steps:

    $ helm3 2to3 convert zenko -t helm --dry-run
    $ helm3 2to3 convert zenko -t helm
    $ helm3 2to3 cleanup -t helm