Prerequisites and system requirements

Supported deployment platforms

You can install the platform hub and the data access layer on k3s, Kubernetes, and Red Hat OpenShift Container Platform.

For capability-specific deployment requirements, see each product's deployment documentation:

• Concert Protect and Concert Resilience: IBM Concert deployment methods
• Concert Optimize: Turbonomic deployment
• Concert Observe: Instana deployment options (Self-hosted Standard Edition, multi-node cluster recommended).

Required tools and cluster

Before you begin the installation, verify that you have the following tools:

kubectl

The Kubernetes command-line tool. See Install kubectl.

Cluster access

You need cluster administrator privileges on a k3s, Kubernetes, or Red Hat OpenShift cluster. k3s is recommended for lightweight or resource-constrained deployments.

Storage class

A Kubernetes storage class must be available in the target cluster. Specify the storage class name in the params.ini configuration file. For k3s deployments, k3s automatically provisions and uses a default storage class.

The platform requires persistent storage that uses the ReadWriteOnce (RWO) access mode. Each volume can be mounted read-write by only one node at a time. PersistentVolumeClaims must specify ReadWriteOnce.

Entitlement and licensing

IBM Concert platform uses an entitlement-based model for image distribution and product licensing.

Entitlement key

You need an entitlement key from your IBM account. The platform installer uses this key to pull container images from IBM Container Registry. You do not download images manually except in air-gapped environments. You provide the entitlement key as a registry credential when you run the installer. You can obtain this key from the container software library on My IBM.

Platform hub license

You must accept a single Concert 3.0 license file when you install the platform hub. Ensure that you read the license and agree to the terms before you accept it. The license is available in the platform installation package at {INSTALL_DIR}/ibm-itom-assembly/license/. You accept the license through an installer flag (--license_acceptance=YES).

TurboLite license

TurboLite, which powers the data access layer, requires its own license file. A temporary license key is available from IBM Passport Advantage when you purchase Concert platform. The Concert platform license keys .zip file includes a temporary Turbonomic license key that works for both TurboLite and Concert Optimize. If you did not purchase Concert Optimize, you use this key only for TurboLite. You apply the license when you install the data access layer.

Capability product licenses

Capability products (Concert, Turbonomic, Instana) retain their existing licensing models. See each product's documentation for licensing requirements.

• Concert Observe: Instana: License activation and renewal
• Concert Optimize: Turbonomic licenses
• Concert Protect and Concert Resilience:
  • Licenses and entitlements (Kubernetes)
  • Licenses and entitlements (VM)

System requirements and sizing

Your system requirements depend on which capabilities you deploy. In addition to the individual capabilities requirements, the platform components require the following resources:

These requirements are based on observed utilization in a test environment where the combined deployment operated within the provisioned capacity with significant memory headroom remaining. Use these utilization metrics as a baseline for capacity modeling and rightsizing. They help you determine the CPU and memory needed to meet target performance and availability.