Post-upgrade setup for Data Privacy

1. Check the migration status for Data Privacy, run:

   oc get pod -n ${PROJECT_CPD_INST_OPERANDS} | grep ikc-couchdb-postgres-data-migration-dp

   Example output:

   ikc-couchdb-postgres-data-migration-dp-b7bbs 0/1 Completed 0

2. Confirm that the migration pod logs end with the following output:

   INFO: migrationStatus: COMPLETE

   and run:

   oc logs -f ikc-couchdb-postgres-data-migration-dp-b7bbs -n ${PROJECT_CPD_INST_OPERANDS}

3. After the data migration is completed, one of the Data Privacy services requires manual scaling (down and up) of the replicas for dp-subset by using the following commands:

   dp_subset_replicas=`oc get deployment/dp-subset -o jsonpath='{.spec.replicas}'`
   oc scale deployment/dp-subset --replicas=0
   oc scale deployment/dp-subset --replicas=$dp_subset_replicas

4. Confirm that the dp-subset pod is up and running after 3-4 minutes:

   oc get pod -n ${PROJECT_CPD_INST_OPERANDS} | grep subset

   and showing the following example output:

   dp-subset-7fbcc9dd4b-rp8zl 3/3 Running 0 4m

If Data Privacy migration job fails when you're following IBM Knowledge Catalog migration steps, specifically step 4, and the state of the migration job is showing the following output:

ikc-couchdb-postgres-data-migration-dp-b7bbs                      0/1     Error   0

you can try to continue with Masking flow service to use Cloudant database for metadata persistence.

1. Run:

   oc patch deployment/dp-subset -n ${PROJECT_CPD_INST_OPERANDS} -p '{"spec":{"template":{"spec":{"containers":[{"name":"dp-subset-metadata","env":[{"name":"DB_TYPE","value":"CLOUDANT"}]},{"name":"dp-subset-jobhandler","env":[{"name":"DB_TYPE","value":"CLOUDANT"}]},{"name":"dp-subset-monitor","env":[{"name":"DB_TYPE","value":"CLOUDANT"}]}]}}}}'

2. Confirm that the dp-subset pod is up and running after 3-4 minutes:

   oc get pod -n ${PROJECT_CPD_INST_OPERANDS} | grep subset

   and showing the expected output:

   dp-subset-7fbcc9dd4b-rp8zl 3/3 Running 0 4m