Upgrade the API Connect Analytics subsystem that was installed on the Linux x86_64
cluster for use in IBM Cloud Pak® for Integration.
Before you begin
This task applies only to deployments where the Management and Portal subsystems were installed
as the API Connect instance on Linux for IBM Z. If you installed all subsystems on Linux x86_64,
follow the instructions in Upgrading all API Connect cluster subsystems on amd64 instead.
Procedure
- 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.9.0 10.0.9.0 20h
-
Update the CR with the new API Connect
license
and
version
.
- Edit the CR by running the following command:
oc edit analyticscluster CR_name -n <APIC_namespace>
- Update the
license
value and API Connect version
;
for example:
apiVersion: analytics.apiconnect.ibm.com/v1beta1
kind: AnalyticsCluster
metadata:
name: production-a7s
spec:
standaloneCluster: true
license:
accept: true
license: L-DZZQ-MGVN8V
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.9.0
storage:
clientAuthEnabled: true
enabled: true
type: shared
shared:
volumeClaimTemplate:
storageClassName: ocs-storagecluster-ceph-rbd
volumeSize: 20Gi
- Save the modified CR and wait for the upgrade to complete.
- Run the following command to verify that the analytics cluster reports all services as
READY:
oc get analyticscluster -n <APIC_namespace>
What to do next
Review the changes in this release, described in What's New in API Connect in the API Connect
documentation.