D2iQ Dispatch: A Cloud-Native CI/CD Platform Built for Kubernetes

Continuous DeliveryContinuous Integration

YOUR COSMETIC CARE STARTS HERE

Find the Best Cosmetic Hospitals

Trusted • Curated • Easy

Looking for the right place for a cosmetic procedure? Explore top cosmetic hospitals in one place and choose with confidence.

“Small steps lead to big changes — today is a perfect day to begin.”

Explore Cosmetic Hospitals Compare hospitals, services & options quickly.

✓ Shortlist providers • ✓ Review options • ✓ Take the next step with confidence

Originally reported by devclass.com. Original post date: March 12, 2020.

D2iQ Expands Into CI/CD With Dispatch

D2iQ — the company formerly known as Mesosphere — extended its Kubernetes portfolio by releasing Dispatch, a cloud-native CI/CD platform integrated directly into its Konvoy Kubernetes distribution. The move signals D2iQ’s intent to offer a more complete platform story, covering not just cluster management but also the continuous integration and delivery pipelines that run on top of those clusters.

Core Design Philosophy: Separation of Concerns and GitOps

Dispatch is designed around two guiding principles: a clear separation of responsibilities between developers and operators, and a GitOps-first approach to pipeline and application configuration. In practice, this means that both pipeline definitions and deployment configuration live in a Git repository, giving every stakeholder a single, version-controlled source of truth for the state of the system.

This GitOps model is increasingly common in the cloud-native ecosystem, but Dispatch’s integration with D2iQ’s existing toolchain — including Konvoy and the Kommander cluster management layer — gives it a tighter operational context than standalone CI/CD tools typically provide.

Multi-Language Pipeline Configuration

One of Dispatch’s headline differentiators is its support for four domain-specific languages for writing pipeline configuration:

  • JSON — familiar to most developers and widely tooled
  • YAML — the de facto standard in Kubernetes-adjacent tooling
  • CUE — a configuration language derived from JSON with added constraints and data validation
  • Starlark — a Python-like scripting language originally developed for the Bazel build system, designed to be deterministic and embeddable

Most competing CI/CD platforms in the cloud-native space default to YAML exclusively. Offering CUE and Starlark alongside the more common formats gives teams with complex pipeline logic more expressive options, and reduces the friction of adopting the tool for teams already working in those languages.

Built on Tekton and Argo CD

Dispatch does not build its execution engine from scratch. According to D2iQ, it is designed to work alongside Tekton (a Kubernetes-native CI/CD framework originally from Google) and Argo CD (a declarative GitOps continuous delivery tool for Kubernetes). This means Dispatch acts partly as an orchestration and configuration layer on top of established CNCF-ecosystem components, rather than reinventing the underlying pipeline execution model.

Multi-Tenancy via Kubernetes Namespaces

Dispatch leverages Kubernetes’ native namespace model to deliver built-in multi-tenancy. Teams can run their pipelines in isolated namespaces, providing resource separation and access control without requiring a separate tenancy management system. This is a practical advantage in enterprise environments where multiple teams share the same cluster infrastructure.

Context: A Crowded CI/CD Landscape

Dispatch arrived into an already busy space. The cloud-native CI/CD problem was prominently discussed at KubeCon Europe 2018 in Copenhagen, which prompted a wave of new projects across the ecosystem. By the time Dispatch launched, the CI/CD section of the cloud-native landscape included dozens of projects at varying stages of maturity.

This level of competition cuts both ways. It validates the problem space, but it also raises the bar for differentiation. Dispatch’s primary advantages — GitOps integration, multi-language support, and tight coupling with D2iQ’s Konvoy and Kommander toolchain — are most compelling for teams already invested in the D2iQ ecosystem.

Availability and Trial

At the time of this report, Dispatch was available to try for free as part of the Konvoy trial offering. The trial bundle also included:

  • A declarative universal operator for managing Kubernetes workloads
  • Kommander — D2iQ’s tool for federated, cross-cluster management

This bundled approach reflects D2iQ’s broader strategy: positioning Konvoy not just as a Kubernetes distribution, but as an integrated platform for running production workloads end-to-end, from cluster provisioning through to continuous delivery.

Summary

Dispatch represents D2iQ’s entry into the cloud-native CI/CD market, with a design that prioritizes GitOps workflows, multi-language flexibility, and Kubernetes-native multi-tenancy. Its reliance on Tekton and Argo CD as underlying components gives it a foundation in proven open-source tooling, while its integration with Konvoy and Kommander makes it a natural fit for existing D2iQ customers. Teams outside the D2iQ ecosystem will need to weigh those integration benefits against the crowded field of alternatives.

0 0 votes
Article Rating
Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x