Installation and deployment
Refer to the topics in this section to learn more about setting up your instance for each
deployment method and adding new users from your organization.
Concert deployment methods
Concert is available as a software-as-a-service (SaaS) or as an on-premises solution by deploying to a virtual machine (VM) or deploying to a Kubernetes cluster using Red Hat® OpenShift® Container Platform (CPFS managed OCP), Red Hat OpenShift Container Platform (without CPFS), Amazon Elastic Kubernetes Service (EKS) , or IBM® Cloud Kubernetes Service (IKS) .
Provisioning Concert (SaaS)
You can provision and manage a SaaS instance of IBM Concert from the IBM SaaS Console, a unified platform for managing all of your IBM SaaS subscriptions, instances, and user access.
Obtaining an IBM entitlement API key
All IBM Concert images are accessible from the IBM Entitled Registry. You must use a valid IBM entitlement API key to pull images for installation or for mirroring to a private container registry.
Deploying on a virtual machine (VM)
Refer to the following details and instructions to deploy IBM Concert as a package of containerized services on a Linux® virtual machine (VM). The package includes scripts and utilities for you to set up and operate the Concert services.
Deploying on Kubernetes
Concert have multiple on-premises deployment options. Deploying Concert software on Kubernetes for container orchestration is achieved through various platforms, including CPFS managed OpenShift Container Platform , OpenShift Container Platform (without CPFS), Amazon Elastic Kubernetes Service (EKS) , and IBM Cloud Kubernetes Service (IKS) .
Implementing IBM watsonx.ai (on-premises)
If using an on-premises version of IBM Concert , you are entitled to an instance of watsonx.ai that you can connect to enable AI functionality in your Concert instance.