Updating script-installed deployments
You can reconfigure and update the software that is already installed. You can modify the installed software, remove it, and add new components. An update to the custom resource (CR) overwrites the deployed resources. The operator applies the changes during the control loop (observe, analyze, act) that occurs as a result of constantly watching the state of the Kubernetes resources.
Before you begin
If you plan to remove capabilities, make sure that you back up the databases, the files that are stored on the persistent volumes, and any other data that you want to keep.
ICP4ACluster
). All the relevant
changes are passed down to the lower-level CRs. If you update, for example, the FNCM CR YAML file
(Content
) directly in your CP4BA multi-pattern deployment, then these changes are
overwritten when the ICP4ACluster
CR is reconciled. To update data source sections
for the FNCM capability in a CP4BA multi-pattern deployment, edit the ICP4ACluster
CR and the CP4BA operator then passes these changes to the lower-level operator.About this task
The following progress bar shows you where you are in the installation process. You can click the completed parts in the diagram to go back and check that you did everything that you needed to do.

You must use the same CR YAML file that you deployed with the operator to make the updates. For example, scripts/generated-cr/ibm_cp4a_cr_final.yaml.
Kind
parameter to Content
instead of
ICP4ACluster
. true
or false
values in the
Form View, but the other parameters need to be done in the YAML
View. You can access the custom resource from the YAML tab, or by
clicking . 
You can make your update to the custom resource file by running the deployment script if you used the script to generate it. You select an existing installation in the script user interface and the file that you used is located by the script. You do need to apply the modified CR after you enter your changes in the user interface.
You can also edit the file manually. The following steps go through the manual procedure, but you can replace steps 2 and 3 by running the deployment script to make the update. For more information, see Option 1a: (Recommended) Generating the custom resource with the deployment script.
Procedure
Results
If changes applied by the operator or other modifications that are made in the environment do not provide the expected result, restart the pods by scaling the impacted deployments down to 0. Scale the pods back up to have Kubernetes (OpenShift) terminate the existing pods and create new ones.
If you changed the IBM Navigator plug-ins, you must restart the pod for the changes to show up.