Server Host Requirements

Kondukto server requirements depend on whether the installation is PoC or Production.
On this page, you may find out which system resources you should allocate for your Kondukto instance.

All-In-One Installation

PurposeCoresRAM (GB)Disk Space (GB)OSWeb ServerOther Required Software
Kondukto PoC41690Debian or Redhat-based distrosLatest NginxLatest Docker & Docker Compose
Latest Git
Kondukto Production832250Debian or Redhat-based distrosLatest NginxLatest Docker & Docker Compose
Latest Git
**MongoDB > 4.2.7

** Note: This is optional, and if your organization does not prefer to use Docker for the database environment, it will be necessary.

📘

The database will be on a Docker container during the PoC phase to be able to act quickly.

❗️

The server will also need to connect to the components (Jira, Jenkins, etc.) that Kondukto will be orchestrating.

Distributed Installation

This installation option can be applied depending on the usage intensity of Kondukto.

Usage intensity depends on the number of the following values:

  • Projects
  • Users
  • Scans
ServerCoresRAM (GB)Disk Space (GB)OSWeb ServerOther Required Software
Application Server43290Debian or Redhat-based distros, Arch LinuxLatest NginxLatest Docker & Docker Compose
Latest Git
Database Server832250--MongoDB > 4.2.7

📘

This installation is recommended when the resources of the Docker database environment or the server that is used as both application and database servers are insufficient.

🗂️

By default, Kondukto uses "SCRAM-SHA-1" & "SCRAM-SHA-256" for the DB authentication mechanism.

Network Requirements

Kondukto host should be able to reach the following services:

  • Your Application Lifecycle Management(ALM) tools such as Github, Gitlab, etc.,
  • Issue Manager Service,
  • Your Scanner Tools,
  • Docker.hub and/or your private container registry

Best Practices For The Kondukto Environment

  • If you are using AWS, the Kondukto Application Server would be more performant with r5.xlarge type of instances and gp3 disks.
  • Installing the DB as a cluster would make your environment more redundant against possible corruption issues. It will also make the I/O faster.
  • It's recommended to get a daily backup of the environments to have data recovery plans.