Upgrading IBM Cloud Pak for Network Automation in a connected environment

Upgrade the Cloud Pak on a cluster that is connected to the internet.

1. Verify that the operator is installed and running by using the following command:

   oc get deployment -n ${NAMESPACE}

   If the operator is installed and running, the following information is included in the output:

   ibm-tnc-orchestration-controller-manager          1/1     1            1           76s

2. Delete the subscription and the cluster service version (CSV) for the operator by running the following commands:

   oc delete subscription ibm-tnc-orchestration-subscription
   oc delete csv ibm-tnc-orchestration-operator.v<operator_version>

   <operator_version> is the version of the existing operator.
3. (Upgrading to 2.7.3 only) Upgrade the IBM Cloud Pak foundational services. To upgrade, specify the subscription channel as v4.6, by using the console. For more information about how to upgrade foundational services, see IBM Cloud Pak foundational services Upgrading foundational services online.
4. Create a YAML file and add the following resource definition. Replace <namespace> with the namespace where IBM Cloud Pak for Network Automation is installed.

   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
       name: ibm-tnc-orchestration-subscription
       namespace: <namespace>
   spec:
       channel: v2.7 
       name: ibm-tnc-orchestration-operator
       source: ibm-operator-catalog
       sourceNamespace: openshift-marketplace

5. Update the operator subscription by running the following command. Replace <filename> with the file that you created in the previous step.

   oc create -f <filename>

   After a few minutes, the IBM Cloud Pak for Network Automation operator is installed with the updated subscription.

6. Identify the available versions of IBM Cloud Pak for Network Automation that you can upgrade to by running the following command:

   oc get orchestration <instance_name> -o jsonpath='{.status.versions.available}'

   Tip: You can upgrade only to the next version in sequence. For example, if your current version is 2.7.4, you cannot upgrade directly to 2.7.6. You must first upgrade to 2.7.5 and then upgrade to 2.7.6. For more information about supported upgrade paths, see Upgrading.
7. Verify that the upgrade of the operators succeeded. Run the following command:

   oc get csv

   Confirm that each of the following operators has Succeeded in the Phase column:

   • IBM Cloud Pak for Network Automation Orchestration Manager
   • IBM Cloud Pak foundational services
   • Operand Deployment Lifecycle Manager
   • IBM Common UI
   • IBM IM Operator
   • IBM Zen Service
8. Update the version of IBM Cloud Pak for Network Automation that runs on your orchestration instance by running the following command:

   oc patch orchestration <instance_name> --type=merge --patch '{"spec":{"version": "2.7.6" }}'

   <instance_name> is the name of your orchestration instance. The command completes the upgrade by updating and restarting some of the pods. When the command is complete, the following output is displayed:

   orchestration.tnc.ibm.com/<instance_name> patched

9. Optional: If you created a customized ingress domain, and you want to use a customized hostname for the IBM Cloud Pak console, you must update the hostname for the console's route. The hostname that you use must include your customized domain name. For detailed steps, see Updating custom hostname and TLS secret by using a configmap.