While multi-site Kubernetes orchestration has numerous benefits, all of which have the potential to translate into a significant competitive edge, it still largely remains elusive — at least in the vendor space. The reason? Well, multi-site configuration is hard and, since during the first adoption wave, the focus was mainly on one cloud (most enterprises start with simple projects), there wasn’t a real need for it.

As we see cloud strategies maturing and enterprises seeking to further optimize cloud usage, the demand for multi-cloud, multi-region, multi-data center, and hybrid is increasing and Kublr 2.0. will fill that gap.

Why you should care about multi-cloud

Multi-site deployments have numerous benefits, the six most important are:

  • Run highly available (HA) apps on Kubernetes
  • Improved reliability
  • Avoid vendor lock-in
  • Optimize for ROI
  • Decrease latency
  • Lower DDoS attack risk

How big of a deal this is depends on your applications. While no one wants downtime, for enterprises in verticals such as banking or telecom, the ability to increase reliability by distributing mission-critical applications among data centers or regions is huge.

Reliability has always been a concern and addressed in the past. However, available solutions that solve the multi-site challenge can’t connect Kubernetes clusters running in different locations — Kubernetes has different specifications that these solutions do not account for.

Kubernetes-focused solutions, on the other hand, handle the deployment and management of Kubernetes clusters in one specific environment but don’t solve the multi-site challenge. Managed services by cloud providers such as EKS, AKS, GKS are one example. There is no overarching layer that allows to reliably orchestrate containers and Kubernetes clusters across different infrastructures — until now.

Why does this matter? We see numerous enterprises spending significant resources bringing new Kubernetes solutions to life and then ending up with a platform that works only for one environment. Often custom-built, these platforms can take six to nine months to get up and running, and then, suddenly, excited about the first success, IT decides to expand only to find out the platform doesn’t meet the needs of the new project.

Kublr 2.0., the Answer to Multi-Site Orchestration

To enable true application reliability, Kublr 2.0. provides multi-site orchestration for Kubernetes management — the first on the market so far. Kublr 2.0. will support multi-site, multi-datacenter, multi-region, multi-cloud, and hybrid deployments across all public clouds and on-prem. It provides customers with a reliable mechanism to react and recover from disaster and failovers, as well as orchestrate and optimize Kubernetes deployments across different sites.

A Private Preview is now available. Kublr 2.0. is currently running at a selected set of customers and we are looking to expand the private preview user base early in 2020. Sign up here.