Checking the deployment type and license
Whatever capabilities you included in your custom resource, you must add the new mandatory parameters and license type.
About this task
Do not modify the values for meta.labels.release or spec.appVersion now. Do it later in the process during the Editing the custom resource for upgrade task.
Any changes to the v5.6.0 custom resource definition (CRD) for the FNCMCluster custom resources impact all FNCMCluster deployments in the cluster. All CRs, even those not targeted for an upgrade to v5.5.9 or higher now, must be modified to meet the requirements of the new CRD specification.
- For CRs earlier than v5.5.9 and targeting v5.5.9 or later:
-
Retain the current syntax for spec.license with the corresponding string value "accept". Add a new syntax for spec.license.accept with the boolean value of true.
-
If present, modify any resources values for cpu within any component to ensure that it is represented as a string value by placing the value in double quotation marks. If they are not enclosed in double quotation marks, the operator does not process the CR. For example, for an earlier version, if the CPU resource values for a component were specified as
cpu: 1
andcpu: 500m
, for v5.5.9 and later, you need to specify the value ascpu: "1"
andcpu: "500m"
, respectively. - Additionally, make the changes suggested in the following table:
Table 1. New and changed shared_configuration parameters in V5.5.9 and later Configuration parameter Comment spec.license.accept Must exist with the value "true".
The values can be removed from the tag parameters if you want to use the digest value. For more information, see Digests versus image tags.
Procedure
- Make a backup of the custom resource YAML file that you used to deploy FileNet Content Manager.
- Set the value of
spec.license.accept
to true.