How To
Summary
This article discusses the effects of the embedded Postgres license key expiration on API Connect environments on Kubernetes, VMWare and OpenShift and offers guidance on remediation steps. The existing embedded Postgres license key is scheduled to expire on 1 October, 2024. After the expiration, some of the database operations will cease to function and might cause downtime.
Objective
If you installed API Connect on OpenShift or CP4I, then refer to https://www.ibm.com/support/pages/node/7158681 If you installed API Connect on Kubernetes and VMWare, then follow the procedure in this article. License expiry date: 1 October 2024, at 00:00:00 (midnight) UTC. After the license expiration, the PostgreSQL cluster instances (pods) and the data will remain available, but the operator will cease any reconciliation attempt on the PostgreSQL cluster with an expired license key, effectively stopping the management of its status. This includes self-healing and high availability capabilities, such as automated failover and primary instance switchovers. Symptoms include the failure to switch over the primary instance to the standby instance after network outages or reboots. You can review the "licenseExpiration" in the PostgreSQL cluster description for the existing license key expiration date. The following command will display the namespace, PostgreSQL cluster, and the current expiration date for all the PostgreSQL clusters on API Connect environments kubectl get cluster.postgresql -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"\t"}{.metadata.name}{"\t"}{.status.licenseStatus.licenseExpiration}{"\t"}{.status.licenseStatus.licenseStatus}{"\n"}{end}' Example output: apic management-16779bce-db 2024-10-01T00:00:00Z Valid license (IBM - Data & Analytics (Cloud))
Steps
Manually updating the license key:
IBM Fix Central download link - https://ibm.biz/BdaRHJ
On Kubernetes:
1. Download `postgres-patch.zip` file from IBM Fix Central and unzip it's contents. 2. Load the `postgres-provider-patch.tar` image into local docker registry, tag and push the image to the k8s registry where other images are present. docker load -i postgres-provider-patch.tar docker tag ibm-apiconnect-management/edb-postgres-license-provider:updated <local-registry-location>/edb-postgres-license-provider:updated docker push <local-registry-location>/edb-postgres-license-provider:updated 3. Update the `<namespace>` and `<image>` fields in the `license-job-k8s.yaml` to the namespace where API Connect is installed and the image to the location in the k8s registry 4. Run the license job kubectl apply -f license-job-k8s.yaml -n <namespace> 5. Verify the license is updated by running the following command kubectl get cluster.postgresql -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"\t"}{.metadata.name}{"\t"}{.status.licenseStatus.licenseExpiration}{"\t"}{.status.licenseStatus.licenseStatus}{"\n"}{end}' Example output after patching the license: apic management-16779bce-db 2999-12-31T00:00:00Z Valid license (IBM - Data & Analytics (ibmda_cloudpak)) On VMWare: 1. Download `postgres-patch.zip` file from IBM Fix Central and unzip it's contents. 2. Copy `postgres-provider-patch.tar` to every management subsystem VM and run the following command as root user: ctr -n k8s.io image import postgres-provider-patch.tar 3. Copy `license-job-ova.yaml` to any management subsystem VM and run the following command as root user: kubectl apply -f license-job-ova.yaml 4. Verify the license is updated by running the following command kubectl get cluster.postgresql -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"\t"}{.metadata.name}{"\t"}{.status.licenseStatus.licenseExpiration}{"\t"}{.status.licenseStatus.licenseStatus}{"\n"}{end}' Example output after patching the license: apic management-16779bce-db 2999-12-31T00:00:00Z Valid license (IBM - Data & Analytics (ibmda_cloudpak))
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8m50000000L0rvAAC","label":"API Connect"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.7"}]
Was this topic helpful?
Document Information
Modified date:
23 September 2024
UID
ibm17169689