Upgrade the API Connect Gateway subsystem on the [amd64] 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 gateway cluster CR's name by running the following command:
oc get gatewaycluster -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-gw 2/2 Running 10.0.8.5 10.0.8.5-3522 20h
-
Update the CR with the new API Connect
license and
version.
- Edit the CR by running the following command:
oc edit gatewaycluster CR_name -n <APIC_namespace>
- Update the
license value and API Connect version;
for example:
apiVersion: gateway.apiconnect.ibm.com/v1beta1
kind: GatewayCluster
metadata:
name: production-gw
spec:
license:
accept: true
license: L-DZZQ-MGVN8V
use: nonproduction
apicGatewayServiceTLS:
secretName: gateway-service
profile: n3xc4.m8
apicGatewayPeeringTLS:
secretName: gateway-peering
version: 10.0.8.5
tokenManagementService:
enabled: true
storage:
storageClassName: <block_storage>
volumeSize: 30Gi
gatewayEndpoint:
annotations:
cert-manager.io/issuer: <apiconnectCluster_name>-ingress-issuer
apicGatewayServiceV5CompatibilityMode: false
adminUser:
secretName: admin-secret
datapowerLogLevel: 5
gatewayManagerEndpoint:
annotations:
cert-manager.io/issuer: <apiconnectCluster_name>-ingress-issuer
- Save the modified CR and wait for the upgrade to complete.
- Run the following command to verify that the gateway cluster reports all services as
READY:
oc get gatewaycluster -n <APIC_namespace>