Remove template overrides from your analytics CR

If you are upgrading to v10.0.5.4 or previous, remove any analytics CR template overrides.The v10.0.1 and v10.0.4 analytics CR template overrides are not compatible with v10.0.5 and must be removed.

Note: If you are using a top-level CR, you must edit the top-level CR instead of the subsystem CR. If the section you want to edit is missing from the top-level CR, copy it from the subsystem CR and paste it into the top-level CR.

If you are upgrading to v10.0.5.5 or later, then template overrides are automatically removed in the upgrade, and no action is needed. If you are upgrading to v10.0.5.4 or a previous v10.0.5 fix pack, then review your analytics CR, and if it has a template: section, remove this section. For example:

oc edit a7s -n <namespace>

Remove the template: section:

# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: analytics.apiconnect.ibm.com/v1beta1
kind: AnalyticsCluster
...
spec:
...
  template:  # REMOVE THIS SECTION
  - name: storage-data
    containers:
    - name: storage-data
      env:
      - name: ES_JAVA_OPTS
        value: "-Xms2g -Xmx2g"
      resources:
        requests:
          memory: 3Gi                    
        limits:
          memory: 4Gi

In this example, the template section specified custom memory allocations for internal analytics processes. These settings are applicable only to pre-v10.0.5 analytics deployments. v10.0.5 has additional deployment profiles that provide increased memory allocations: Analytics component deployment profile limits.