Release v2.1.9

    • This release addresses a security vulnerability found in Rancher: the default admin account that is created when Rancher is first launched will be recreated on subsequent restarts of Rancher, even if the account was explicitly deleted by a Rancher administrator. This poses a security risk because the account is recreated with Rancher’s default username and password. You can view the official CVE here CVE-2019-11202.
    • In Rancher 2.0 and 2.1, the auto generated certificates for Rancher provisioned clusters have 1 year of expiry. It means if you created a Rancher provisioned cluster about 1 year ago, you need to rotate the certificates, otherwise the cluster will go into a bad state when the certificate expires. Rancher v2.2.x provides UI support for certificate rotation. In Rancher 2.1.9, the rotation can be performed from Rancher API, more details are . image is made available in and Rancher helm repos.
    • Clusters created through Rancher can sometimes get stuck in provisioning [#15970] [] [#15695]
    • The upgrade for Rancher node-agent daemonset can sometimes get stuck due to pod removal failure on a Kubernetes side []
    • Fixed the situation where self signed certificate used for communication with a standalone Rancher server could expire. [19156]
    • Fixed an issue where disk space was reported low in the UI even when there was no disk pressure []
    • rancher/rancher:v2.1.9
    • rancher/rancher-agent:v2.1.9

    Rancher supports both upgrade and rollback starting with v2.0.2. Please note the version you would like to upgrade or to change the Rancher version.

    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.