X

The latest cloud infrastructure announcements, technical solutions, and enterprise cloud insights.

Hybrid and Multi-Cloud Are Tired. Federated Distribution Is Wired! Announcing D2iQ Support for Container Engine for Kubernetes

Gilson Melo
Director of Product Management

As part of our continuing commitment to open standards and supporting a broad and varied ecosystem, we’re pleased to announce that D2iQ (formerly Mesosphere) has extended its Multi-Cloud Federate Governance application support to Oracle Cloud Infrastructure Container Engine for Kubernetes (sometimes referred to as OKE).

This post was written by a guest contributor, Chris Gaun, Product Manager at D2iQ. Most the content was previously published in a D2iQ blog post.

Despite vast enhancements in cloud technology, little has changed in hybrid and multi-cloud strategy for a decade. Although Kubernetes has made implementation easier, the basic goal is the same as ever: deliver identical infrastructure management across on-premises and public clouds.

It’s time for this strategy to evolve. We can do that by deploying the distribution that’s needed for “Day 2” cloud operations to the existing Kubernetes implementations that are everywhere—thanks to OKE, Google’s GKE, Amazon’s EKS, Azure’s AKS, DIY Kubernetes, D2iQ Konvoy, and others. Users have many, and expanding, Day 2 needs —like wanting to use Thanos and Grafana to monitor all their clusters—that could be easily solved with the fact that Kubernetes is everywhere.

Graphic that shows the Konvoy interface and illustrates how Oracle, Google, Amazon, Azure, and other  Kubernetes products can use supporting products, such as Grafana, kubecost, and Kudo, for security, monitoring, chargeback, authentication, and workload scalability.

While Kubernetes has made setting up the same infrastructure on Oracle, AWS, Google, Azure, and on premises easier, cloud vendors have begun providing Kubernetes services that make managing the cluster lifecycle a breeze. Given this state, in which the same Kubernetes API is readily available from public cloud services and software like Konvoy whether on premises or in the cloud, it’s strange that the hybrid and multi-cloud strategy has largely gone untouched. Given that D2iQ now has the same Kubernetes API everywhere (OKE, EKS, GKE, AKS), why don’t we start thinking about delivering the same operational experience in terms of monitoring, workload configuration, and the like on those clusters?

Federating Your Distribution with Kommander

The Kommander product strategy has always assumed that some users have existing Kubernetes clusters or have already decided on a particular vendor or provider. Kommander still delivers value to those customers. One way that D2iQ planned to do that, even before the first line of code was committed on any of its products, was to take the Day 2 Kubernetes-based add-ons from Konvoy and federate them out to third-party clusters. Doing so makes those clusters Konvoy-like and gives users the same operational view in Kommander no matter which managed cluster lies beneath. Over time, D2iQ will continue to expand its roster of Day 2 add-ons and give operators more consistent capabilities on all their clusters.

The Konvoy Kubernetes distribution itself was architected to treat the lifecycle concerns of Kubernetes separately from the other features one would expect in a distribution—monitoring, logging, UI, and so on. D2iQ wanted the value of the distribution above Kubernetes to come from the fact it’s opinionated, preconfigured, patched and up to date, scanned for security vulnerabilities, bolstered with other D2iQ Kubernetes products (like Dispatch for CI/CD), and tested in real-world scenarios, including at scale. The guiding principle is that the only dependency is on a Kubernetes version and not on anything specific to Konvoy or D2iQ.

Kubernetes components sitting above the Konvoy CLI and sitting below Kubernetes-based add-ons and Ksphere products such as Kommander.

With the latest Beta of Kommander released recently, D2iQ can now federate out these Day 2 add-ons, starting with single sign-on and monitoring. As of the time of the release of this blog post, logging wasn’t available yet, but it’s coming soon.

What’s Next

Ultimately, D2iQ is working on the backend by the next general availability (GA) release to make it easy to expand what gets federated out to third-party clusters. We also want to give users the choice to federate some stacks (for example, monitoring) and not others (for example, logging) in case they have solutions, like Splunk, already in place. When making these clusters Day 2 ready and Konvoy-like, D2iQ wants to give users the same experience of having a stack that’s opinionated, preconfigured, patched and up to date, scanned for security vulnerabilities, and tested in real world scenarios—including at scale. But like Konvoy, we also want to allow them the freedom to choose the tools and solutions that fit their organization.

Getting Started

First, if you don’t already have an Oracle Cloud account, sign up for a free trial today. Then, get a copy of the newest Beta version of Kommander. If you’re an existing D2iQ customer, you can download the Kommander v1.1 in the Support Portal. If you are not an existing customer, you can contact the D2iQ team. Additional details can be found in the Konvoy 1.5 and Kommander 1.1 GA announcement.

After you obtain your copy of the software, follow the instructions to deploy Kommander to start deploying, monitoring, and managing your Oracle Container Engine for Kubernetes cluster.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.