Impact of embedded Postgres license expiry

License expiry date: October 1st, 2024, at 00:00:00 (midnight) in UTC.

All IBM Cloud Pak operators released before June 2024 that use the Embedded EDB PostgreSQL cluster as a database are affected.  

Cloud Pak operators affected.

The Cloud Pak operators deployed using the IBM Foundational services operator (CPFS)version 3.19.21, version 3.23.13, or version 4.6.1 or below will have the license key expiring on October 1st, 2024 

Following cloud Pak products and operators using the embedded EDB PostgreSQL database are affected by the embedded Postgres license expiry:

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 your cloud pak environment. 

oc 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: 
 
cp4i          keycloak-edb-cluster   2024-10-01T00:00:00Z Valid license (IBM - Data & Analytics (Cloud))
cpd-instance  zen-metastore-edb      2024-10-01T00:00:00Z Valid license (IBM - Data & Analytics (Cloud))
cpd-instance2 zen-metastore-edb      2024-10-01T00:00:00Z Valid license (IBM - Data & Analytics (Cloud))

Resolution:

Updating the license key automatically by upgrading CPFS operator: 

 EDB postgreSQL versions older than 1.18.x  have been End of Life and no longer supported by EDB.  You can no longer use the documented workaround to update the license Key .  You should upgrade the EDB version to 1.18.x or above and upgrade the  IBM Foundational Services to version 3.19.22, version 3.23.14, or version 4.6.2 as appropriate for the cloud Pak. 

The IBM Foundational Services operator (CPFS) version 3.19.22, version 3.23.14, or version 4.6.2, or above will install a later version of the EDB PostgreSQL operator and update the license key expiration date 2999-12-31 .  

oc get job -A | egrep "NAME|create-postgres-license-config" 

Example output :
NAMESPACE     NAME                            COMPLETIONS  DURATION  AGE
cp4i          create-postgres-license-config  1/1          17s       218d
cpd-operator  create-postgres-license-config  1/1          17s       218d

You will find the job under the same namespace where the postgresql-operator-controller-manager-xxx pod is deployed and manage multiple postgreSQL clusters. This operator can manage multiple  
Depending on the cloud pak operators and operand deployment patterns on the OCP cluster, you may find the postgresql-operator-controller-manager under multiple namespace

namesapce=<NAMESPACE1> 

​​​​oc get job create-postgres-license-config -n $namespace -o yaml | \
sed -e 's/operator.ibm.com\/opreq-control: "true"/operator.ibm.com\/opreq-control: "false"/' \
    -e 's|\(image: \).*|\1"cp.icr.io/cp/cpd/edb-postgres-license-provider@sha256:c1670e7dd93c1e65a6659ece644e44aa5c2150809ac1089e2fd6be37dceae4ce"|' \
    -e '/controller-uid:/d' | \
oc replace --force -f - && \
oc wait --for=condition=complete job/create-postgres-license-config -n $namespace

3-- Verify that the embedded Postgres cluster correctly reflects the status of the license expiry. Run the following command:

oc get cluster.postgresql -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"\t"}{.metadata.name}{"\t"}{.status.licenseStatus.licenseExpiration}{"\t"}{.status.licenseStatus.licenseStatus}{"\n"}{end}'

Example of the output after patching all the postgresql clusters:

cp4i          keycloak-edb-cluster   2999-12-31T00:00:00Z Valid license (IBM - Data & Analytics (Cloud))
cpd-instance  zen-metastore-edb      2999-12-31T00:00:00Z Valid license (IBM - Data & Analytics (Cloud))
cpd-instance2 zen-metastore-edb      2999-12-31T00:00:00Z Valid license (IBM - Data & Analytics (Cloud))

cp.icr.io/cp/cpd/edb-postgres-license-provider@sha256:c1670e7dd93c1e65a6659ece644e44aa5c2150809ac1089e2fd6be37dceae4ce 

podman login cp.icr.io -u cp -p '<entitlement-key>'
podman pull cp.icr.io/cp/cpd/edb-postgres-license-provider@sha256:c1670e7dd93c1e65a6659ece644e44aa5c2150809ac1089e2fd6be37dceae4ce
podman tag cp.icr.io/cp/cpd/edb-postgres-license-provider cp.icr.io/cp/cpd/edb-postgres-license-provider:1600
podman push cp.icr.io/cp/cpd/edb-postgres-license-provider:1600 ${PRIVATE_REGISTRY_LOCATION}/cp/cpd/edb-postgres-license-provider:1600

#skopeo inspect docker://${PRIVATE_REGISTRY_LOCATION}/cp/cpd/edb-postgres-license-provider:1600 --tls-verify=false
{
  "Name": "test:5000/cp/cpd/edb-postgres-license-provider",
  "Digest": "sha256:5ea15c640c66100179c9f33161aa8af774075ba33a8463a837d75f4937f5bbb4",
  "RepoTags": [
    "1600"
  ],
  "Created": "2024-05-07T10:25:34.699036409Z",
  .......
}

$PRIVATE_REGISTRY_LOCATION:port/cp/cpd/edb-postgres-license-provider@sha256:c1670e7dd93c1e65a6659ece644e44aa5c2150809ac1089e2fd6be37dceae4ce