We adopted it as we think it's a strong technology. The other bit that's new in 2.0 is Flux for continuous delivery. Once those clusters are brought up, Kommander has a whole set of Day 2 operations capabilities. Kommander and DKP 2.0 are built on top of cluster API so they can manage the life cycle of any Kubernetes cluster on any infrastructure. It's important to have that central point of control. Today, We see the world is moving towards multi-cloud, hybrid cloud, and edge. We did that because we want DKP and especially Kommander, which is one of the products in the platform, to be the central point of control for the enterprise to manage the entire Kubernetes fleet. We've learned a lot there and built the roadmap for 2.0 together with our customers.ĭKP 2.0 is a significant re-architecture of the platform. It's the culmination of everything that we learned from our customers running it in production since we released 1.0. Tobi Knaup: Version 2.0 is always special for any software company. InfoQ: Why is DKP 2.0 a significant release for D2iQ? InfoQ sat with Tobi Knaup, CEO of D2iQ, at KubeCon+CloudNativeCon NA 2021 and talked about DKP 2.0, its relevance to developers, and the future of Kubernetes. Also, it has auto-scaling capabilities for workloads to improve availability and support for immutable operating systems such as Flatcar Linux. The new release provides a single pane of glass for managing multi-cluster environments and running applications across any infrastructure including private cloud, public cloud, or at the network edge.ĭKP 2.0 is built on the Cluster API, a Kubernetes sub-project to simplify creating, configuring, and managing multiple clusters, to support Day 2 operations out of the box.

D2iQ recently released version 2.0 of the D2iQ Kubernetes Platform (DKP), a platform to help organizations run Kubernetes workloads at scale.

Train to pakistan study guide