Rancher Release - v1.3.0

Release v1.3.0


Note: With our new infrastructure services, we no longer launch a network agent and have moved to a specific HAProxy image for load balancers. Therefore, we no longer need rancher/agent-instance.


  • Starting with version 1.2.0, Rancher no longer supports AWS ELBs and only supports AWS ALB (Application Load Balancers). Please update your high availability setups to use ALBs.
  • When upgrading from prior v1.2.x releases, please check your infrastructure stacks to make sure your services are up to date. If an “Upgrade Available” button is shown, please upgrade to the latest service. Complete upgrading each individual infrastructure stack before moving on to the next stack.
  • For every Rancher release, we have moved to tagging specific load balancer images (i.e. rancher/lb-service-haproxy) for load balancer services. If you have upgraded from a previous version of Rancher and a newer load balancer image has been released, a symbol will appear next to the load balancer name to indicate a newer image is available for that Rancher version. It’s recommended to upgrade to this latest image for load balancers.
  • If you are upgrading from 1.1.x to v1.2.2, please read the v1.2.0 release notes on important notes about the upgrade.

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 use any release with a rc{n} suffix. These rc builds are meant for the Rancher team to test out builds.

v1.3.0 has been tagged as rancher/server:latest.


  • Windows Server 2016 Support - Experimental [#4576] - We are providing an experimental preview into support of Windows containers. Please see Window’s Support for Docker for more details on Docker’s support for Windows containers. In this experimental release, the release is limited to the following features:
    • Adding Windows 2016 server hosts as Rancher agent services.
    • Adding stacks, services, and containers.
    • The only supported network modes are “NAT” and “transparent”.
    • NOTE: Other than noted above, existing Rancher features such as LB services, DNS, and metadata do not currently work yet as they have not been ported to work on Windows containers just yet. Look for it in the future!
  • More Kubernetes Improvements - Added the following additional support:
    • Kubernetes 1.5.1 - k8s 1.5.1 is now supported.
    • SkyDNS Support [#5948] - Starting with Rancher 1.3 + k8s 1.5.1, only SkyDNS will now be offered as the default DNS engine. All RancherDNS entries will automatically be migrated to using SkyDNS and RancherDNS will now be deprecated for k8s.
    • Helm and Dashboard UI [#7003] - Starting with Rancher 1.3, the default k8s dashboard UI and helm support will automatically launched and managed by Rancher.
  • UI Enhancements - More UI features:
    • Added bulk actions and search on the containers page [#342, #1533]
    • Ability to click on stack name in the host view [#2557]

Known Major Issues

  • Hosts in AWS created from v1.1.4 using the UI (aka docker-machine) are not cleaned up properly when deleted from the UI [#6750]
  • With self signed certs, using a remote kubectl client does not work automatically, but there is a workaround in the issue [#7235]
  • With self signed certs and Kubernetes, Helm operations are hanging [#7234]

Major Bug Fixes since v1.2.2

  • Fixed an issue where self signed certs were not working with Rancher server [#6122]
  • Fixed an issue where individual container links were not resolvable [#6584]
  • Fixed an issue where Google Container Registry was not working [#6956]

Rancher-Compose Downloads

Rancher CLI Downloads

1 Like