Integration with Kubernetes Clusters

Cadence.CI integrates with Kubernetes so that Mélodium runners are deployed as pods directly within your cluster. Pipeline execution stays inside your infrastructure, using your existing networking, storage, and compute policies.

How It Works

A lightweight Kubernetes Controller is deployed in your cluster. It watches for runner provisioning requests from Cadence.CI and creates the corresponding pods. When a job completes, it tears down those pods. Cadence.CI never has direct access to your cluster, all interactions go through the controller.

Setup Steps

Deploy the controller: install the Cadence.CI Kubernetes Controller into your cluster. It handles communication between Cadence.CI and your cluster’s API server.
Configure cluster access: the controller uses a service account with the permissions needed to create and delete runner pods, no cluster-admin privileges required.
Runner deployment: when a pipeline runs, Mélodium runners are created as pods in your cluster, using the namespace and resource quotas you configure.
Direct execution: pipeline steps execute inside your cluster, with direct access to cluster-internal services and storage.

Benefits

Security: data remains within your Kubernetes environment throughout execution.
Cost efficiency: runners use your existing cluster capacity, with no additional provisioning.
Compliance: compute stays within your designated cluster, meeting data residency requirements.
Scalability: Kubernetes’ scheduler handles pod placement and resource allocation automatically.
Self-healing: if a runner pod is evicted or crashes, Kubernetes reschedules it and Cadence.CI retries the affected work.

Available Configurations

While Cadence.CI can run on any standard Kubernetes distribution, pre-built cluster configurations are available for specific providers. See the pages in this section for provider-specific setup guides.

Integration with Cloud Providers Build a CI/CD Pipeline