top of page

CONT: Automated Module Packaging & Deployment for IDT Kubernetes Runtime

  • Laura Gavrilut
  • Jun 8
  • 2 min read

The DS2 Containerisation (CONT) module is designed to simplify how applications are packaged and deployed by Dataspace participants in the IDT Kubernetes environment. Instead of dealing with complex Kubernetes configurations, developers only need to provide a simplified Helm Chart descriptor. CONT then automatically combines this with standard templates from the DS2 Portal Marketplace to generate a complete Helm Chart and deploy it.


As a core component of the IDT Broker, CONT ensures that all DS2 modules are deployed in a consistent, automated, and reliable way.


What is CONT?

CONT (Containerisation Module) is a core component of the IDT platform that automatically packages and deploys DS2 modules into a Kubernetes environment. It takes a simple module descriptor based on Flux HelmRelease templates and converts it into a complete Helm chart using standard templates. The chart is then deployed to the IDT runtime using a Flux GitOps workflow.

CONT Features:

  • Kubernetes Native: Built on Kubernetes using open-source tools like Flux and the GitOps Toolkit

  • Deployment Control: Gives admins/SREs control over how and where applications are deployed in the cluster

  • Helm Chart Templates: Supports reusable templates for different application types

  • Web UI: Provides a modern interface to manage containerisation

  • API-Based Management: Manage application lifecycle (create, install, uninstall, delete) via API


Why CONT?

CONT removes the complexity of manual Kubernetes deployments. Instead of building and managing full Helm charts, developers only need to provide a lightweight descriptor based on existing templates. Developers can create this descriptor with zero Kubernetes knowledge. This descriptor is then expanded into a full Helm chart using templates developed by cluster operators.


Cluster operators own the cluster and create Helm chart templates based on how applications need to be deployed. Developers can focus on development while operators remain in control of what is deployed to the cluster. CONT also ensures consistency, speeds up deployment, and supports both manual and automated (GitOps) workflows.


DS2 Architecture Overview

The CONT module is built around a set of Kubernetes native components that work together to automate how modules are created, managed, and deployed in the IDT environment.


At the core is the ChartController, which watches for new or updated HelmChartDescriptors. When a change is detected, it fetches the required base templates from the DS2 Marketplace, combines them with the descriptor, and generates a complete Helm Chart for deployment.


The ChartManager acts as the management layer, allowing users or APIs to create, view, and manage HelmChartDescriptors and deployed charts. It communicates with the Kubernetes cluster to track the current state of applications.


The Installer is responsible for applying everything to the Kubernetes runtime. It installs Helm Charts, descriptors, and related resources into the IDT cluster. This process is based on Flux, the GitOps toolkit.


The Source Controller monitors external repositories (like GitHub) for changes in descriptors and automatically triggers deployments. The Source Manager helps manage these repository connections.


Finally, the Containerisation UI provides a user-friendly interface to monitor deployments, manage resources, and view system status.

Comments


bottom of page