On-Prem Control Plane Deployment

1. CMS Installation

1.1 Docker Installation

Install Docker and required dependencies on the server:

yum install -y yum-utils device-mapper-persistent-data lvm2 sudo yum-config-manager --add-repo https://download.docker.com/linux/rhel/docker-ce.repo sudo yum install -y docker-ce docker-ce-cli containerd.io sudo systemctl enable --now docker sudo docker run hello-world

1.2 Docker Log Configuration

To prevent disk exhaustion caused by high-log-producing containers (e.g. GitLab), configure Docker log rotation.

Edit the Docker daemon configuration:

nano /etc/docker/daemon.json

{ "log-driver": "json-file", "log-opts": { "max-size": "100m", "max-file": "3" } }

Restart Docker:

systemctl restart docker

1.3 Private Registry Login

To pull application images, authenticate to the private Docker registry:

docker login -u krontechdev dckr_pat_sdYRS5K_YEnChJqMuFJbcs1psec

1.4 Docker Compose Installation

Docker Compose version 2.16.0 or higher is required.

sudo curl -SL "https://github.com/docker/compose/releases/download/v2.16.0/docker-compose-linux-x86_64" \ -o /usr/libexec/docker/cli-plugins/docker-compose chmod +x /usr/libexec/docker/cli-plugins/docker-compose ln -s /usr/libexec/docker/cli-plugins/docker-compose /usr/local/bin/docker-compose

1.5 CMS Installation (Internet-Accessible Environment)

If the environment has internet access, images will be pulled automatically.

From the directory containing the deploy YAML file and the ms/ folder:

docker-compose -f deploy-aws-25.3.2.yml -p dsp up -d

1.6 CMS Installation (Offline Environment)

For air-gapped environments, images must be pulled and saved on another server.

Example:

docker save \ krontechdev/dsp-alarm-manager:25.3.2 \ krontechdev/dsp-agent-handler:25.3.2 \ krontechdev/dsp-worker-manager:25.3.2 \ krontechdev/dsp-monitoring:25.3.2 \ krontechdev/dsp-store-manager:25.3.2 \ krontechdev/dsp-json-configuration-manager:25.3.2 \ krontechdev/dsp-portal-ui:25.3.2 \ krontechdev/dsp-portal:25.2.4 \ krontechdev/dsp-process-controller:25.3.2 \ krontechdev/kron-commons-alfred:25.0.13 \ krontechdev/kron-commons-clickhouse:25.0.13 \ krontechdev/kron-commons-notification:25.0.13 \ krontechdev/kron-commons-network:25.0.13 \ krontechdev/kron-commons-auth:25.0.13 \ krontechdev/kron-commons-config:25.0.13 \ krontechdev/kron-commons-license:25.0.13 \ redis:alpine \ gitlab/gitlab-ee:17.2.2-ee.0 \ postgres:16.0-alpine \ | gzip > kron-dsp-allimages-24.5.3.tar

On the target server:

docker load < kron-dsp-allimages-24.5.3.tar docker image ls

Then deploy CMS:

docker-compose -f deploy-aws-25.3.2.yml -p dsp up -d

1.7 GitLab Installation

GitLab is deployed using a separate Docker Compose file and should run independently from CMS.

docker compose -f gitlab.yml -p dsp up -d

CMS and GitLab must use the same Docker network

GitLab UI is accessible via http://<host-ip>:10100 (port configurable)

After startup:

The directory krn-git/ is created automatically

Initial admin password is located at:

krn-git/config/initial_root_password

This file is automatically deleted after 24 hours.

Post-installation steps:

Create a new admin user with full permissions

Create GitLab groups:

product (group)

dsp (subgroup)

Generate a Personal Access Token with full permissions

Update the following files accordingly:

ms/scripts/git/lab/.git-credentials

ms/scripts/git/lab/.gitconfig

Update host-specific IPs in the compose files

Finally, start CMS:

docker compose -f /root/cms/cms-25.2.3.yml -p dsp up -d

If containers exit on first startup, rerun the command. This may happen due to initial health-check dependencies.