Upgrading the Analytics subsystem on Linux x86_64

Upgrade the API Connect Analytics subsystem that was installed on the Linux x86_64 cluster for use in IBM Cloud Pak® for Integration.

1. Run the API Connect pre-upgrade health check:
   1. Verify that the apicops utility is installed by running the following command to check the current version of the utility:

      apicops --version

      If the response indicates that apicops is not available, install it now. See The API Connect operations tool: apicops in the API Connect documentation.

   2. Run the following command to set the KUBECONFIG environment.

      export KUBECONFIG=/<path>/kubeconfig

   3. Run the following command to execute the pre-upgrade script:

      apicops version:pre-upgrade -n <APIC_namespace>

      If the system is healthy, the results will not include any errors.

2. Use the OpenShift web console to upgrade the API Connect operator by changing the subscription channel to the v3.5 version.
   Attention: The operator must be fully upgraded before you proceed to the next step.
3. Get the analytic cluster CR's name by running the following command:

   oc get analyticscluster -n <APIC_namespace>

   Note the CR's name in the NAME column of the response; for example:

   NAME            READY   STATUS    VERSION    RECONCILED VERSION   AGE
   production-a7s   2/2     Running   10.0.5.5   10.0.5.5-3522        20h

4. Update the CR with the new API Connect license and version.
   1. Edit the CR by running the following command:

      oc edit analyticscluster CR_name -n <APIC_namespace>

   2. Update the license value and API Connect version; for example:

      apiVersion: analytics.apiconnect.ibm.com/v1beta1
      kind: AnalyticsCluster
      metadata:
        name: production-a7s
        labels:
          app.kubernetes.io/instance: analytics
          app.kubernetes.io/managed-by: ibm-apiconnect
          app.kubernetes.io/name: apic-dev-a7s
      spec:
        standaloneCluster: true
        license:
          accept: true
          license: L-VQYA-YNM22H
          use: production
        certManagerIssuer:
          name: <apiconnectCluster_name>-self-signed
          kind: Issuer
        ingestion:
          enabled: true
          clientSubjectDN: 'CN=<common_name>'
          clientAuthEnabled: true
          configReloadAutomatic: true
          endpoint:
            annotations:
              cert-manager.io/issuer: <apiconnectCluster_name>-ingress-issuer
        profile: n1xc2.m16
        microServiceSecurity: certManager
        version: 10.0.5.5
        storage:
          clientAuthEnabled: true
          enabled: true
          type: shared
          shared:
            volumeClaimTemplate:
              storageClassName: ocs-storagecluster-ceph-rbd
              volumeSize: 20Gi

   3. Save the modified CR and wait for the upgrade to complete.
5. Run the following command to verify that the analytics cluster reports all services as READY:

   oc get analyticscluster -n <APIC_namespace>