Changing deployment profiles on OpenShift top-level CR

You can change an API Connect top-level CR installation to use different profiles.

Before you begin

This task assumes that you have already deployed an API Connect cluster as explained in Deploying on OpenShift and Cloud Pak for Integration. If you are changing from a one replica profile to a three replica profile, ensure that you have three replica profile hardware (3 worker nodes) available. For more information on the available profiles, see: Deployment and component profiles.

Note: If you have a three replica profile, and want to change to one replica, you must first change your analytics configuration to shared storage. Dedicated storage is not supported on the one replica profile.

Procedure

  1. Verify that the API Connect cluster is in the Ready state by running the following command: 
    oc get apiconnectcluster
  2. Update the API Connect Cluster CR:
    1. Open the API Connect Cluster CR in edit mode by running the following command: 
      oc edit apiconnectcluster <APIC-instance-name>
    2. In the CR, change the spec.profile value to the profile that you want to use.
    3. Save the change by running the following command: :wq
  3. Wait for microservice to scale up, or scale down, as needed.
  4. Verify that the API Connect cluster is in the Ready state by running the following command: 
    oc get apiconnectcluster