Rancher container management platform version 1.5 has officially met with you. The enhancements in this release are designed to enable rancher to better support use in enterprise production environments.
In the new version, additional webhooks fully improve the scalability of rancher, allowing users to highly optimize the utilization of the overall infrastructure. The new API, the new network and container scheduling strategy, provides fine-grained control of the container environment. In addition, there are a series of new functions such as metadata performance enhancement, conditional logic support of catalog template, etc.
More webhooks drivers
In rancher 1.4, we added webhooks and an initial driver to handle the expansion and contraction of containers. The key to implementing webhooks is the “receiver”. The receiver can register webhooks and provide a URL to trigger operations in the rancher software.
Based on the feedback from the community during this period, in rancher 1.5, we extended the implementation of rancher webhooks to two new drivers:
Host scaling: users can create webhooks that can scale hosts (this only applies to hosts created from the rancher API).
Dockerhub service upgrade: webhook is configured to update the dockerhub image, and webhook will be used to update those services that use the dockerhub image in the rancher.
Enhancement of policy control
Rancher 1.5 enhances policy control and supports the interception of all API requests. In addition, pre / post filter logic can be added to each request, which makes it easier for administrators to define and control API access. Users can also add fine-grained API policy management to modify API request and response payloads from the rancher.
Rancher now supports adding two additional network policies per environment configuration. The first network policy allows you to choose to allow or deny traffic other than service. By default, the rancher setting allows communication between all services in the same environment. However, if configured to reject, the container will not be able to communicate with a container outside the service. The second strategy is to provide link support. Those services or stacks configured to deny communication can obtain communication permission by using docker links or selector tags.
Additional policy controls are now also available for container scheduling. Rancher 1.5 supports adding labels that restrict container scheduling to specific hosts. Moreover, the pre specified label will determine the placement of the container, so as to optimize the control of the host.
Metadata performance enhancements
By caching metadata information, we greatly enhance rancher’s metadata service. This reduces database jitter and reduces the space required for metadata delivered to each metadata service. Since many services depend on metadata (of course, it also depends on the specific implementation method of users), you should be able to obviously feel the overall improvement of rancher performance. When you start a large capacity container at the same time, or add a new container after multiple containers have been running, you must also feel the performance enhancement.
Conditional logic support for catalog templates
Rancher can now use conditional logic through the go template system. By combining conditional logic with variable interpolation, you can generate more dynamic catalog templates more flexibly.
We sincerely invite you to download the latest version, and please don’t hesitate to let us know what you think. Our products progress according to the needs of users.