Supported deployment models and upgrade paths

Use this topic to determine the supported deployment models, processor architectures, and upgrade paths for IBM® Concert releases.

Use this information to plan deployments and upgrades across supported IBM Concert environments.

Supported deployment models

The following table shows the supported deployment models and processor architectures for each IBM Concert release.

Table 1. Deployment model and processor architecture support
Version Self-hosted/on-premises Managed Release availability
X86 IBM Power IBM Z AWS Cloud IBM Cloud
VM (Docker/Podman) VM (k3s) EKS OCP RKE2 OCP VM OCP
3.0.1 Discontinued starting with 3.0.0 POC only No No No No No No Yes Yes SaaS only
3.0.0 Yes Yes Yes Yes No No No No No On-premises only
2.4.0 N/A N/A N/A N/A N/A POC only POC only N/A N/A N/A POC only (IBM Power)
2.3.1.x Yes Yes Yes No N/A No No No On-premises only
2.3.0.x No No No No No Yes Yes SaaS only
2.2.0 Yes Yes Yes Yes Yes Yes Yes SaaS and on-premises
2.1.0 Yes Yes Yes Yes No Yes Yes SaaS and on-premises
2.0.0.2 Yes Yes Yes No No Yes Yes SaaS and on-premises
2.0.0.1 Yes Yes Yes No No No No On-premises only
2.0.0 Yes No No No No No No VM only

Definitions used in the deployment support table

The deployment support table uses the following terms and values:
  • Self-hosted (on premises) deployments are installed and managed within your own environment and are upgraded by applying supported IBM Concert releases.
  • Managed (SaaS) deployments are hosted and managed by IBM. New features, enhancements, and fixes become available automatically when IBM deploys a new SaaS release.
  • Discontinued starting with 3.0.0 indicates that x86 virtual machine deployments that use Docker or Podman are no longer supported starting with IBM Concert version 3.0.0. Support for upgrading existing VM (Docker/Podman) deployments to the VM (k3s) deployment model is planned for a future IBM Concert release.
  • POC only indicates a proof-of-concept deployment that is not generally available and is not fully qualified for production use. Contact IBM Support for more information.
  • N/A indicates that the deployment model or processor architecture is not applicable to that release.
  • Yes indicates that the deployment model, processor architecture, or upgrade path is supported.
  • No indicates that it is not supported.
  • Release availability identifies whether a release is available for self-hosted deployments, managed (SaaS) deployments, or proof-of-concept (POC) environments.
Note: For IBM Z deployments, use IBM Concert for Z. IBM Concert for Z has a separate release lifecycle and documentation. For more information, see the IBM Concert for Z documentation.

Supported upgrade paths

The following table shows the supported upgrade paths between IBM Concert releases.

A supported upgrade path indicates that an existing deployment can be upgraded directly from the source release to the target release.

Table 2. Supported upgrade paths
From version To version X86 IBM Power IBM Z
VM (Docker/Podman) VM (k3s) EKS OCP RKE2 OCP VM OCP
2.3.1.x 3.0.0 Discontinued starting with 3.0.0 No No No No No No N/A
2.2.0.x 3.0.0 No No No No No No
2.3.1.x Yes N/A Yes Yes N/A No N/A
2.1.0.x 3.0.0 N/A No No No No No No
2.3.1.x Yes N/A Yes Yes N/A No N/A
2.2.0 Yes N/A Yes Yes N/A Yes N/A
2.0.x 3.0.0 N/A No No No No No No
2.3.1.x Yes N/A Yes Yes N/A No N/A
2.2.0 Yes N/A Yes Yes N/A Yes N/A
2.1.0.x Yes N/A Yes Yes N/A N/A N/A
Note:
  • Support for upgrading from a VM (Docker/Podman) deployment to a VM (k3s) deployment model is planned for a future IBM Concert release.
  • IBM Concert 2.4 was available only for proof-of-concept (POC) deployments and was not released as a generally available version. As a result, supported upgrade paths to or from version 2.4 are not included in the following table. If you are using a POC deployment of IBM Concert version 2.4, contact IBM Support for upgrade guidance.