Rancher 1.4 is out today! As always, we encourage you to review the release notes. However, we’d like to run through a few notable changes, and the rationale behind them here.
First, we’ve continued our move towards a friendlier Kubernetes experience by transitioning to Dashboard and Helm, which replace the Rancher Kubernetes UI and Catalog Kubernetes templates, respectively. We started this move in 1.3 as both Dashboard and Helm have matured tremendously in the past year, and we feel they’ve reached production stability and feature parity with what they’re replacing. Our goal at Rancher Labs is always to support mainstream container technologies, and integrating Dashboard and Helm is a natural part of that philosophy.
In this release, we’re also including:
Webhooks: Naturally, as container usage grows, so does demand for webhooks as both are well-suited for optimizing your infrastructure usage. In Rancher 1.4, we implement webhooks as its own microservice, and an initial driver for scaling. We’ll dive into this in more detail with another blog post this week, but we’re pleased to begin working more with our community on webhooks, particularly on new drivers and functionality.
Network Policies: Starting with 1.4, we will provide more fine grained control of network policies within an environment. Initially, we will allow the ability to set basic ALLOW or DENY default policies for container network access. With each subsequent release, more features, such as allowing inter-service access but denying intra-service communications, will be possible.
Secrets Management: In 1.4, we’ve also introduced the ability to handle secrets within Rancher using Vault Transit. Previously, secrets could be managed with third-party solutions via Rancher catalog, but as growing numbers of users utilize Rancher and containers in production, it makes sense to build this functionality directly into our platform.