Rancher Labs announced the general availability of Rancher 2.2, introducing new features to simplify the provisioning of enterprise-grade Kubernetes by IT operators and giving developers even more control over their applications.
With Rancher 2.2, teams who build software can now worry less about the infrastructure and focus more on accelerating innovation and driving business value.
“As Kubernetes adoption grows exponentially, IT operators have been asking for an easy, reliable and repeatable way to provision, manage and support enterprise-grade Kubernetes clusters across on-premise and cloud infrastructures,” said Sheng Liang, CEO and co-founder of Rancher Labs. “The Rancher 2.2 GA has several capabilities to satisfy these requirements, including automated etcd backup and restore for disaster recovery, a multi-tenant catalog for greater privacy in sensitive projects, and the ability to create and manage global DNS to deliver highly available applications spread across multiple clusters.”
Combined with previously announced features like support for multi-cluster applications and advanced monitoring powered by Prometheus, the Rancher 2.2 GA release is Rancher Labs’ most significant release to date. Enterprise customers are already using many capabilities in preview mode and have reported huge benefits to their Kubernetes operations.
New features in the Rancher 2.2 GA include:
- Global DNS: Provides public access to applications deployed in multiple clusters or multiple projects within the same cluster by automatically programming a hostname of services to public DNS. This release includes support for Route53 and AliDNS, with alpha support for CloudFlare. Support for additional providers is under development.
- Cluster BDR (Backup and Disaster Recovery): Perform scheduled and ad hoc snapshots of etcd from the Rancher UI, API, or the Kubernetes API, writing to local storage, mounted shared storage, or any S3-compatible object store. Users can restore snapshots through the Rancher UI, making it simple to include backups as a part of every cluster deployment.
- Multi-tenant catalogs: With multi-tenant catalogs, users can isolate catalogs by cluster or project, providing granular isolation such that even the app names cannot be shared across projects.