Association between DG Operator and DG Server version/DG Operands

Solution Verified - Updated

Environment

  • Red hat OpenShift Container Platform (OCP)
    • 4.x
  • Red Hat Data Grid (RHDG)
    • 8.x
    • Operator

Issue

  • How verify the DG Operator version with DG Operand (server) version?
  • Which DG Operator supports which DG version?
  • A new patch has been release for DG Server 8.4.4 in Sept 28th, do we need to upgrade the OCP Data Grid Operator to have that patch?

Resolution

Verify the version via the DG Operator manager logs, which will list the images it supports - if it is not listed the Infinispan CR will not be accepted as explained on Data Grid 8 Operators coexistence in the same Openshift cluster:

DG Operator 8.4.8 list:

$ oc project openshift-operators
$ oc get pod
NAME                                                      READY   STATUS    RESTARTS   AGE
infinispan-operator-controller-manager-id  1/1     Running   0          9m
$ oc logs infinispan-operator-controller-manager-id
...
"downstream-version": "8.4.1-3" <--------------------------------------------------- 8.4.1-3
"image": "registry.redhat.io/datagrid/datagrid-8-rhel8@sha256:985193caf9bc3698c4d85aeedd1cfea09bccda881636d67885387b2a83c65ebd",
"cve": true,
"deprecated": false
},
{
"upstream-version": "14.0.9",
"downstream-version": "8.4.2-1" <--------------------------------------------------- 8.4.2-1
"image": "registry.redhat.io/datagrid/datagrid-8-rhel8@sha256:9d9e466b7c367d0406406550c74bc790aa68f3f875ea4f652eb28f2e25a05458",
"cve": false,
"deprecated": false
},
{
"upstream-version": "14.0.11",
"downstream-version": "8.4.3-1" <--------------------------------------------------- 8.4.3-1
"image": "registry.redhat.io/datagrid/datagrid-8-rhel8@sha256:424b30dccd773f69c079b35a42e8c3e339246c5d490e14e3fcfb8bd8144a9160",
"cve": false,
"deprecated": false
},
{
"upstream-version": "14.0.11",
"downstream-version": "8.4.3-2" <--------------------------------------------------- 8.4.3-2 (cve)
"image": "registry.redhat.io/datagrid/datagrid-8-rhel8@sha256:554b831a0803d55a4e3b7022011b5a5f6d2b4b65009065a9b28bc8e55fc3ad46",
"cve": true,
"deprecated": false
},
{
"upstream-version": "14.0.17",
"downstream-version": "8.4.4-1" <--------------------------------------------------- 8.4.4-1
"image": "registry.redhat.io/datagrid/datagrid-8-rhel8@sha256:9223b4b5c1c866a91033dac40f30a4caae0f6946cdb64935a3fdfffdb9ede660",
"cve": false,
"deprecated": false
}
]

Root Cause

As explained in the solution Data Grid 8 Operators coexistence in the same Openshift cluster the DG 8.4.x.csv provide the feature to use more than one DG server image, aka Operand, which is set via spec.Image in the Infinispan CR - however, downgrade is not allowed: deploying an Infinispan CR yaml with 8.4 cannot be changed for a lower version.

Data Grid Operator version 8.4.x supports the following Data Grid versions (non-complete table):

Data Grid Operator versionOperand versions
DG 8.4.88.3.1-1, 8.4.0-1, 8.4.0-2, 8.4.1-1, 8.4.1-2, 8.4.1-3, 8.4.2-1, 8.4.3-1, 8.4.3-2, 8.4.4-1,
DG 8.4.78.3.1-1, 8.4.0-1, 8.4.0-2, 8.4.1-1, 8.4.1-2, 8.4.1-3, 8.4.2-1, 8.4.3-1, 8.4.3-2
DG 8.4.18.4.0-1, 8.4.0-2, 8.3.1-1
DG 8.38.3.1-1

The above means the DG Operator 8.4.1 can be launched with three Infinispan CR with three different DG 8 versions: two versions DG 8.4 and one DG 8.3.

CVE images:

The DG Operand version has spin images and have -x extra id, and this is listed as cve:true.
Example:

"upstream-version": "14.0.11",
"downstream-version": "8.4.3-2" <------------
"image": "registry.redhat.io/datagrid/datagrid-8-rhel8@sha256...",
"cve": true, <-----------------------------
"deprecated": false
}

DG unknown version:

For example to use DG 8.4.4 server it needs DG Operator 8.4.8. The user cannot set image 8.4.4-1 when using the Operator 8.4.7. Otherwise, it won't accept - it will return:

Danger alert:Error
   Fix the following errors:
     Error "Invalid value: "8.4.4-1": unknown version: 8.4.4-1" for field "spec.version".

If a spec.version is not valid, then the Infinispan CR webhook will reject it when a user tries to create the resource.

Diagnostic Steps

  1. Verify the DG Operator manager for the version it supports/allows.
  2. If DG unknown version the current DG Operator does not support the DG server.
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.