Release v2.1.3

    With this release, the following versions are now latest and stable:

    • Clusters created through Rancher can sometimes get stuck in provisioning [] [#15969] []
    • The upgrade for Rancher node-agent daemonset can sometimes get stuck due to pod removal failure on a Kubernetes side [#16722]
    • Added updated Kubernetes versions (i.e. v1.10.11, v1.11.5, v1.12.3) to address for clusters launched by Rancher. The default Kubernetes version is v1.11.5. [16835]
    • rancher/rancher-agent:v2.1.3

    Due to the HA improvements introduced in the v2.1.0 release, the Rancher helm chart is the only supported method for installing or upgrading Rancher. Please use the Rancher helm chart to install HA Rancher. For details, see the .

    If you are currently using the RKE add-on install method, see Migrating from a RKE add-on install for details on how to move to using a helm chart.

    Note: When rolling back, we are expecting you to rollback to the state at the time of your upgrade. Any changes post upgrade would not be reflected. In the case of rolling back using a , you must specify the exact version you want to change the Rancher version to, rather than using the default tag.

    Note: If you had the helm stable catalog enabled in v2.0.0, we’ve updated the catalog to start pointing directly to the Kubernetes helm repo instead of an internal repo. Please delete the custom catalog that is now showing up and re-enable the helm stable. [#13582]