The software company D2iQ, formerly Mesosphere, has released D2iQ Kubernetes Platform 2.0. The new release has D2iQ Konvoy 2.0 and D2iQ Kommander 2.0 on board and subjects the platform to structural changes. They should make it easier to deal with distributed infrastructures.
Successor to Mesosphere-DC / OS
At the end of last year, D2iQ disbanded the Mesosphere DC / OS platform to instead focus on the D2iQ Kubernetes Platform (DKP). The company has stabilized them in order to meet the highest requirements of large customers when using Kubernetes. DKP is intended to offer a range of functions that is largely the same as Mesosphere DC / OS or to go beyond that in some points. One of the advantages of DKP is that it is based on pure upstream open source Kubernetes and thus a vendor lock-in can be avoided.
Version 2.0 revises the architecture
The new release DKP 2.0 has some changes under the hood, behind which a fundamental change should be: According to a D2iQ blog post Version 2.0 is supposed to “radically simplify” the execution of applications in distributed, heterogeneous infrastructures in multi-cluster and multi-tenant environments – be they on-premises, in the cloud, in the edge area or in an air gap, like it since Konvoy 1.3 is possible.
This should be achieved by DKP 2.0 acting as a centralized, strategic control point for the application infrastructure of a company and carrying out the change from a prescriptive to a declarative approach: Many previously manual processes for executing a project and managing its life cycle should be automated with version 2.0.
Cluster API and Flux CD
In the course of the architectural change, DKP 2.0 uses the Cluster API and Flux CD projects, both of which originate from the Cloud Native Computing Foundation (CNCF). Cluster API should enable the automated tuning and scaling of available resources in order to adapt the performance depending on the workload and to minimize costs. The collection of continuous delivery tools for Kubernetes Flux CD is intended to offer GitOps possibilities.
In addition, D2iQ Kommander 2.0 is to be the central control point for the platform in the future. It offers a renewed GUI for the Kubernetes distribution Konvoy, the DKP CLI can also continue to be used.
Interested can be found in the D2iQ blog more information about D2iQ Kubernetes Platform 2.0.