Release v1.5.2
Versions
- rancher/server:v1.5.2
- rancher/agent:v1.2.1
- rancher/lb-service-haproxy:v0.6.2
- rancher-v0.5.1
- rancher-compose-v0.12.4
Supported Docker Versions
Docker 1.10.3
Docker 1.12.3-1.12.6
Docker 1.13.1 (Not supported with Kubernetes as Kubernetes does not support it yet)
Docker 17.03.0-ce (Not supported with Kubernetes as Kubernetes does not support it yet)
Rancher Server Tags
Rancher server has 2 different tags. For each major release tag, we will provide documentation for the specific version.
-
rancher/server: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/server:stable
tag will be our latest stable release builds. This tag is the version that we recommend for production.
Please do not the releases with a rc{n}
suffix. These rc
builds are meant for the Rancher team to test out builds.
Stable - v1.5.2 - rancher/server:stable
Important - Upgrade
-
In this release, we will automatically upgrade the
network-services
infrastructure stack as without this upgrade, your release will not work. Please expect this automatic upgrade regardless of yourupgrade.manage
setting.- Upgrading from versions prior to Rancher v1.5.0 will trigger an automatic upgrade.
- Upgrading from Rancher v1.5.0 to Rancher v1.5.1 will not trigger an automatic upgrade.
-
With the upgrade manager, you can update your settings to always have your infrastructure stacks upgraded to the latest default version after upgrading Rancher server. This can be updated under Admin -> Settings -> Advanced Settings and the setting is
upgrade.manager
. By default, this is turned off.
Known Major Issues
Major Bug Fixes since v1.5.1
- Fixed an issue where if there is an environment with no hosts, after upgrading and adding the hosts, the
network-services
infrastructure stack, which is required to be upgraded, will not upgrade immediately. It will be delayed by an hour. [#8047] - Fixed an issue where If there is an environment with
disconnected
hosts, thenetwork-services
infrastructure stack, which is required to be upgraded, will not upgrade immediately. When the host becomesactive
, it will eventually upgrade an hour later. [#8048]