Deckhouse Code organizes collaborative work between software development and operations teams: it covers code storage and versioning, code review, CI/CD pipelines, and delivery to target environments.

Deckhouse Code covers the following scenarios:

  • storing and versioning Git repositories, including forks, protected branches, and pull mirroring;
  • reviewing and merging changes through merge requests with approval rules and merge trains;
  • running CI/CD pipelines defined in .gitlab-ci.yml;
  • managing projects, groups, and access rights;
  • scanning code for vulnerabilities and tracking dependencies, in Enterprise Edition.

Installation types

Deckhouse Code is delivered as a Linux package, an Omnibus Docker image, a Helm Chart or a Deckhouse Kubernetes Platform module.

Installation type What it is When it applies Installation documentation
Linux package Deckhouse Code installed from a .deb or .rpm package on a single host For a host running a supported Linux distribution directly, without a container or a Kubernetes cluster Quick start
Omnibus Docker Deckhouse Code running as a single container built from the same omnibus package For a host running Docker instead of the package directly Quick start
Helm Chart Deckhouse Code deployed to a Kubernetes cluster with a Helm chart, without the Deckhouse Kubernetes Platform operator For a Kubernetes cluster managed independently of Deckhouse Kubernetes Platform Quick start
Deckhouse Kubernetes Platform module Deckhouse Code installed and managed by an operator through the CodeInstance resource For a Deckhouse Kubernetes Platform cluster Deckhouse Kubernetes Platform module

Integrations

Deckhouse Code supports the following integrations:

Next steps

Deckhouse Code is available in Standard Edition and Enterprise Edition; see Editions for the feature differences.

For instance administration, see the Administration Overview. For everyday work with projects, repositories, and merge requests, see the Usage Overview.