Rancher 2.2: heads-up on change in server-chart versioning

Table of Contents

March 22, 2019

This advisory was first communicated by email, on the date mentioned above, to all Rancher customers with a then active support subscription.

Dear Rancher User,

We are getting really close to our planned release of Rancher 2.2.0 on Tuesday, March 26th. This email is intended to give you a heads-up on a change we are making as part of this release.

We will be changing Rancher Server chart versioning scheme from the current "datestamp" style (2019.1.x) to versions that match the Rancher Server release (2.1.x).   With the release of 2.2.0, the previous "datestamp" style releases will be removed from the repo and replaced by charts versioned in step with the Rancher Server version, as illustrated by the table below:


Previous Chart Version
New Chart Version
App (Rancher) version
2019.3.1 2.1.7 v2.1.7
2019.1.2 2.1.6 v2.1.6
2019.1.1 2.1.5 v2.1.5
2018.12.4 2.1.4 v2.1.4
2018.12.1 2.1.3 v2.1.3
2018.11.1 2.1.2 v2.1.2
2018.10.2 2.1.1 v2.1.1
2018.10.1 2.1.0 v2.1.0


What does this mean for you?

In most situations, no action will be required on your part.

  • The new Rancher versioned charts are exactly the same to their equivalent "datestamp"  versioned chart.
  • Current Rancher Server chart installations will continue to run without interruption.  
  • Helm "install" and "upgrade" actions that don't specify the --version flag will continue to use the latest version of Rancher. No additional configuration is necessary.
  • Helm "install" and "upgrade" actions that do specify the --version flag will need to use the equivalent Rancher versioned chart instead of the "datestamp" version.

When is this change happening?

This change will be just prior to the release of Rancher Server v2.2.0, currently scheduled for next week.  It will be executed the day before Rancher v2.2.0 ships.  At this point, we expect this to be early next week and will notify you once we complete it.

The new replacement charts (2.1.0 - 2.1.7) are already in the helm chart repos and available for use.

Why did we need to make this change?

In the process of creating security updates for the 2.0.x series, we discovered that the "datestamp" style of versioning we had adopted with the 2.1.x release would not allow us to easily create security updates to the 2.1.x series once we released 2.2.0.

For more details and history of our Rancher Server chart versioning, please see this GitHub issue:


If there are any questions, simply submit a request via this portal referencing this article and we will track and respond to your question as a Support Ticket.

Rancher Support Team

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.