Skip to content

Self Hosted Premium required

Installing KNIME Business Hub on-premises requires the Self Hosted Premium package. This package is automatically included on your Salesforce Quote or Order Form for all net-new self-hosted installations from April 1, 2026 onwards. Contact your KNIME account manager if you have questions about licensing.

Prerequisites

This page covers what must be in place before installing KNIME Business Hub via Argo CD.

For supported Kubernetes versions, see Supported Environments.

Hardware Requirements

The following requirements apply to the cluster nodes running KNIME Business Hub. Argo CD itself should be provisioned separately and its resource usage does not count toward these figures.

CPU Generation Requirement

The CPU must be from 2011 or newer, as older processors may lack required instruction sets (SSE4.2 for Keycloak, AVX for the event-dispatcher).

Linux Kernel Compatibility

Avoid Linux kernels 6.12–6.14 due to known CPU and memory issues. This affects Ubuntu 24.04 AMIs, RHEL, Amazon Linux, and managed clusters. Check your kernel version with uname -r before installation.

Recommended Requirements

The values below are recommendations. Actual requirements depend on your specific workloads and usage patterns.

ResourceRecommended
CPU28+ vCores total (10 core + 16 execution)
Memory64 GB+ (24 GB core + 40 GB execution)
Disk1 TB+

Only x86, x64, and x86_64 processors are supported.

Required Command-Line Tools

Install the following tools on the machine you use to manage the cluster:

Argo CD

Argo CD 3.3 or later must be installed and running in the cluster before deploying KNIME Business Hub. See the Argo CD Getting Started guide for general installation instructions. For production environments, install Argo CD via Helm and configure ingress.

Required Cluster Components

Istio

Istio 1.28.3 or later is required as the ingress and service mesh layer for KNIME Business Hub. Contact your KNIME representative for the required configuration.

Network Plugin (CNI)

A CNI plugin must be installed in the cluster. Consult your Kubernetes distribution's documentation for supported CNI options.

Storage Driver (CSI)

A CSI driver with support for persistent volume claims must be installed. The storage class used must support the ReadWriteOnce access mode at minimum. KNIME Business Hub uses the cluster's default storage class automatically. Services that use persistent volume claims individually support a storage class override via local-values.yaml.

Optional: Prometheus CRDs

If Prometheus monitoring is enabled, the Prometheus Operator CRDs (ServiceMonitor, PodMonitor) must be installed before deploying KNIME Business Hub.

Optional: Metrics Server

For Horizontal Pod Autoscalers, install metrics-server.

External Systems

KNIME Business Hub requires two external systems that must be provisioned and accessible from the cluster before installation.

Object Storage

KNIME Business Hub requires object storage for artifacts, content, and execution data. AWS S3, MinIO, and other S3-compatible systems are supported, as well as Azure Blob Storage.

The storage account must have read and write permissions on the required buckets. Administrative permissions are not required. Contact your KNIME representative for the number of buckets required and the exact access configuration.

For cloud-specific infrastructure setup guides, see:

PostgreSQL Database

KNIME Business Hub requires PostgreSQL 16 or later. Managed services such as AWS RDS, Azure Database for PostgreSQL, and GCP Cloud SQL are supported.

Contact your KNIME representative for the connection configuration.

Airgapped Installations

For installations in environments without access to public registries, KNIME provides an airgap bundle containing all required container images and Helm charts.

To perform an airgapped installation:

  1. Set up a private registry — Provision an OCI-compatible container image registry and a Helm chart registry accessible from the cluster.
  2. Obtain the airgap bundle — Contact your KNIME representative to obtain the airgap bundle for your target version.
  3. Push images and charts — Extract the bundle and push the images to your private registry and the charts to your private chart repository.
  4. Configure the installation — Update your configuration to pull images and charts from your private registry instead of the public KNIME registry. Refer to the configuration repository provided by your KNIME representative for the override structure.