Let’s explore the new software and features in the latest release of Rancher, which you can use by running the rancher/server:v1.6.11 image. Check our documentation on Installing Rancher Server if you need help running Rancher.
NOTE: Keep in mind that Rancher v1.6.11 is tagged as latest, which means it’s not ready for production use. Our current, stable version recommended for use in production is Rancher v1.6.10.
We’ve added Kubernetes 1.8.3 to this release. For all the information on new features and improvements in Kubernetes 1.8, see the release blog post. This update also allows you to run Docker 1.12.6, 1.13.1, and 17.03.2, as Kubernetes 1.8 supports these versions.
Use Azure Load Balancer by using type: LoadBalancer
Use Azure Blob/Managed Disks by specifying kind: StorageClass and kind: PersistentVolumeClaim
Mount Azure File share by using azureFile inside a volumes definition.
Ability to Change Subnet for Kubernetes
In previous configurations, the Kubernetes subnet was hardcoded to 10.43.0.0/16. Now parameterized, you can configure all the parameters to your liking.
The latest stable version, Docker 17.09, is supported when using Cattle orchestration.
Draining Connections on Load-Balanced Services
Are you getting HTTP Bad Gateway (502) errors when upgrading a load-balanced service? Rancher v1.6.11 comes with a load balancer that can drain connections before stopping the container. Inside the load-balanced service definition in rancher-compose.yml, it is now possible to specify drain_timeout_ms as an amount of milliseconds to wait before stopping the container. Check out the Rancher Docs for more information.
Clustered MySQL Support
We’ve had a large number of requests to be able to use Rancher with a clustered MySQL setup which requires a primary key on all tables, like Percona XtraDB with pxc_strict_mode = ENFORCING or MASTER or some cloud solutions. By adding --db-strict-enforcing to the docker run command, you can now use those clustered databases as database for Rancher.
Prune Services No Longer Specified in Rancher CLI
The Rancher CLI v0.6.5 now compares the specified services in the current stack to those in the new stack. If a service is no longer specified in the new stack, it will be removed when you use rancher up --prune.
Infrastructure Services Updates & Fixes
Here’s a quick mention of some great improvements to infrastructure services:
GitHub issue 9957 — We’ve applied CPU restrictions to the metadata container, which should help in the events of scaling up. Before, the load on the systems could get really high which could impact the services running on it.
GitHub issue 9971 — This is a huge improvement on the IPsec side. Tunnels that were interrupted would not recover after a certain period of time, but in this release we included retry logic to re-establish those connections.
Hopefully, you all enjoy the new, improved stuff on which the team has been working hard. This post includes a subset; read the full release notes to see what else is new and improved. You can also subscribe to the Rancher Forums announcements so you get a notification every time there is a new release.
For Kubernetes users, be aware of this bug that will restart all containers when you upgrade to version 1.8.