Deploying Cloud Pak for Integration demos

• Create a secret called ibm-entitlement-key in the namespace where the Demos instance will be created. The secret must contain cp as the username, cp.icr.io as the docker server, and an entitlement key as the password. Get an entitlement key from the IBM Container Library.

• If you wish to configure API Connect with a specific mail server create a secret called cp4i-demo-apic-smtp-secret in the namespace where the Demos instance will be created. The secret needs to contain the emailAddress, mailServerHost, mailServerPassword, mailServerPort and mailServerUsername.

• Install the individual product operators you need for the specific version of Cloud Pak for Integration that you are installing. For 2022.4 channel versions, see Operator channel versions for this release. For more information about installing the operators, see Installing the operators by using the Red Hat OpenShift console or Installing the operators by using the CLI.

• Install Openshift Pipelines operator (if installing the demos operator at namespace scope).

• Create a catalog source for the demos operator by applying the following yaml:

  apiVersion: operators.coreos.com/v1alpha1
  kind: CatalogSource
  metadata:
    name: ibm-integration-demos-operator-catalog
    namespace: openshift-marketplace
  spec:
    displayName: IBM Cloud Pak for Integration Demos
    publisher: IBM
    sourceType: grpc
    image: icr.io/cpopen/ibm-integration-demos-catalog:latest

• Install the Demos Operator at the same scope as the Cloud Pak for Integration operator.

• Install the Platform UI, using the procedure in Deploying the Platform UI. Do not proceed until the deployment is completed.

Storage: Cloud Pak for Integration demos use both Read Write Many (RWX) and Read Write Only (RWO) modes of storage, depending on the capabilities required.

Minimum resources required to run the demos are:

Car Crash Repair

Driveway Dent Deletion

Event-Enabled Insurance

Mapping Assist

Scope of the demo operator

Deployment with the Red Hat OpenShift web console

1. Navigate to the OpenShift web console.

2. In the navigation panel, click OperatorHub, search for Demo, then click IBM Cloud Pak for Integration Demos.

3. Click Install.

4. Click Demo.

5. Create the Demo custom resource (CR) in the UI or with the YAML editor.

   • Select the project in which to create the CR:

     • Deploy in the same project (namespace) as the Demos operator, if the Demos operator was installed in the A specific namespace on the cluster installation mode.

     • Deploy in any project (namespace) if the Demos operator was installed in the All namespaces on the cluster installation mode.

   • For guidance on which licenses to select, see Licenses.

     Note: Non-production licenses for App Connect and MQ are required, and all licenses need to be accepted in order to proceed.

The following is an example Demo CR. Replace <user-namespace> and <user-values> with the appropriate values.

apiVersion: integration.ibm.com/v1beta1
kind: Demo
metadata:
  name: demo-setup
  namespace: <user-namespace>
spec:
  addons:
    elasticSearch: true
    ocpPipelines: true
    postgres: true
  demos:
    cognitiveCarRepair: false
    drivewayDentDeletion: false
    eventEnabledInsurance: true
    mappingAssist: false
    weatherChatbot: false
  general:
    storage:
      block:
        class: cp4i-block-performance
      file:
        class: ibmc-file-gold-gid
  license:
    accept: false
    ace: L-APEH-CJUCNR <non-prod-licenses>
    demo: L-RJON-CJR3Q4 <non-prod-licenses>
    apic: L-GVEN-GFUPVE <non-prod-licenses>
    ar: L-RJON-CD3JKX <non-prod-licenses>
    mq: L-RJON-CJR2RX <non-prod-licenses>
  products:
    aceDashboard: true
    aceDesigner: false
    apic: true
    assetRepo: false
    eventStreams: true
    mq: true
  version: 2022.4.1

Additional information:

• Driveway Dent Deletion Demo: Link

• Event Enabled Insurance: Link

• More demos: Link

• Installation is based on the k8s Operator.

To create multiple instances of the demo operator in each namespace, you need to:

• Install operators for Platform UI, API Connect, App Connect, Asset Repository, Event Streams, MQ, and Operations Dashboard. See Installing the operators with the OpenShift console or Installing the operators with the CLI for more information.

• Get the secret to pull in the demo operator image.

Select the product licenses that correspond to the version of Cloud Pak for Integration you are using for a demo. Click any of the links for details about specific license terms.

2022.4.1 licenses

• Only runs on AMD64 architectures

• Only runs on Linux operating systems

• For a non-production environment, only (licenses shown in the CR are non-production licenses)

• Users need entitlement (for example, an entitlement key) to cover instances deployed as the part of the demo.

This chart is supported on Red Hat OpenShift. The predefined SecurityContextConstraint name privileged has been verified for this chart.

Custom SecurityContextConstraints definition:

+kubebuilder:rbac:groups=security.openshift.io,resources=securitycontextconstraints,resourceNames=privileged,verbs=use

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  creationTimestamp: null
  name: manager-role
rules:
- apiGroups:
  - security.openshift.io
  resourceNames:
  - privileged
  resources:
  - securitycontextconstraints
  verbs:
  - use