Release v2.0.1
- rancher/rancher:v2.0.1
- rancher/rancher-agent:v2.0.1
Rancher Server Tags
Rancher server has 2 different tags. For each major release tag, we will provide documentation for the specific version.- rancher/rancher:latest
tag will be our latest development builds. These builds will have been validated through our CI automation framework. These releases are not meant for deployment in production.- rancher/rancher:stable
tag will be our latest stable release builds. This tag is the version that we recommend for production.
Latest - v2.0.1 - rancher/rancher:latest
Stable - v2.0.0 - rancher/rancher:stable
Rancher supports both upgrade and rollback starting with v2.0.1. Please note the version you would like to upgrade or rollback to and follow the instructions to change the Rancher version.
New Enhancements
- Added ability to import/export Workloads/Services/Namespaces as a YAML [#12371]
- Added ability to mark RoleTemplates as [] - This will allow admins to control the ability to select when adding members to clusters and projects.
- Rancher CLI Enhancements
By embarking on the Rancher 2.0 project, all of the legacy Rancher 1.6 Java modules were completely rewritten in Go, and in the process touched just about every other module in the system. As such, there will not be a direct upgrade from 1.6.x to 2.0.
We do plan to continue to support Rancher 1.6.x for at least another year after 2.1 has been released to give our users time to plan this migration.
Known Major Issues
- Unable to authenticate Github []
- After upgrade, ingresses may have some issues with showing 503s or inability to target new workloads, the current workaround is to re-create the ingress [#13649, ]
- Fixed an issue where specifying address/internal-address wasn’t working when adding a custom host [#11365]
- Fixed an issue where embedded elastic search does not start []
- Fixed an issue where active directory was slow to search for AD setups with a lot of users [#13232, , #13421]
- Fixed an issue where azure with azure cloud provider wouldn’t start correctly []
- Fixed an issue where rancher/agent wouldn’t log errors if the configured cacerts were not equal to the retrieved certificate [#13244]
- Fixed a couple of issues relating to storage [, #13198]
- Fixed