Customer Managed Installation Requirements

Before you begin, it's important to decide how you'll install the Kinetic Platform. Your choice depends on two factors: whether your environment has internet access and how you'll manage your Kubernetes deployment. In simple terms, you need to determine if your system can pull resources directly from the internet or if you'll work in a closed (air-gapped) setup, and whether you'll use your own Kubernetes cluster or rely on our provided Kubernetes installer. This decision will guide the specific requirements and steps you need to follow.

Environment Connectivity

Internet-Accessible Environment:
If your environment has internet access, the Kinetic Platform installation will pull required packages, Docker container images, and other resources directly from the internet. Our installation process will handle downloading and configuring these dependencies automatically.

Air-Gapped Environment:
If your environment does not have internet access, you will need to manually provide all required resources. Pay close attention to the air-gapped installation requirements when bringing your own Kubernetes Cluster, as all necessary images and dependencies must be pre-loaded into your environment before installation.

Deployment Options

The Kinetic Platform runs on a Kubernetes-based architecture, consisting of multiple containerized applications that work together to provide the full Kinetic experience. To install the Kinetic Platform, you need a Kubernetes environment. The best deployment method depends on your infrastructure setup and technical expertise. We offer two options:

Bring Your Own Kubernetes Cluster:
You provide and manage your own Kubernetes infrastructure.
Detailed requirements

Provided Kubernetes Installer:
A tailored installer deploys Kubernetes along with the Kinetic Platform on your servers.
Detailed requirements

For more details view our Deployment Option Recommendation Guide

Installation Dependencies (External to Kubernetes)

The following dependencies must be configured before installing the Kinetic Platform. These components are external to Kubernetes but are essential for a successful deployment.

Networking & Connectivity

DNS & Domain:
A fully qualified domain name (FQDN) is required for the platform.

Load Balancer:
Your load balancer must support sticky sessions using a session cookie (e.g., INGRESSCOOKIE).

Firewall Settings:
Ensure all necessary ports are open for communication between platform dependencies and the Kubernetes environment.

View Detailed Networking and Connectivity requirements

Certificates

TLS Certificates:

A wildcard TLS certificate is required to secure all subdomains. Alternatively, you can specify all subdomains you intend to use as Subject Alternate Names (SANs) in your certificate. However, this restricts the ability to create new spaces in the Kinetic Platform without updating the certificate for your domain name.
When using the provided Kubernetes installer, an additional TLS certificate can be optionally provided to secure the installation dashboard. Otherwise, a self-signed certificate is used (not recommended for production).

View Detailed Certificate Requirements

Databases

The Kinetic Platform relies on multiple database technologies for different functionalities:

SQL Database (PostgreSQL Required):

PostgreSQL is required for workflow and integration functionalities.
Each space in your Kinetic Platform installation requires its own database with appropriate permissions for your workflow engine and your integration service.

Cassandra (Required for Core Application Functionality):

The Kinetic Platform requires a Cassandra database to manage core application operations.

Elasticsearch (Optional for Logging Capabilities):

Used for logging capabilities within the platform.
If Elasticsearch is not provided, logging features dependent on it will be disabled.

View Detailed Database Requirements

Storage Requirement

Persistent Storage (NFS Required):

The Kinetic Platform requires Network File System (NFS) for persistent storage.
NFS is used to store shared application data, configurations, and stateful components.
Ensure your NFS setup meets the required performance and capacity specifications.

Detailed NFS Requirments