Release v1.3.3
Versions
- rancher/server:v1.3.3
- rancher/agent:v1.1.3
- rancher/lb-service-haproxy:v0.4.9
- rancher-compose-v0.12.1
- rancher-v0.4.1
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.
Important
- Rancher has re-introduced being able to use ELBs with this release.
- 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, 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:latesttag 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:stabletag 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.3 has been tagged as rancher/server:latest and rancher/server:stable.
Infrastructure Services Note
We have added a new scheduler entry, which should be upgraded before network-services as it fixes a bug when upgrading network-services.
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]
- After container restart, DNS resolution may be delayed before being available [#7402]
Major Bug Fixes since v1.3.2
- Fixed an issue where
kubectl execwas not working behind ALBs by enabling the ability to set up ELBs. Setting up ELBs require extra steps and additional steps with SSL [#7464]