Preparing to install Watson Knowledge Catalog

Plan and prepare to install Watson™ Knowledge Catalog.

Before you begin

Complete these tasks before you install Watson Knowledge Catalog.

Migrating legacy components to Version 4.7

Starting in Version 4.7, all legacy features for Watson Knowledge Catalog will not be available and users will need to migrate their data from legacy services before upgrading to Version 4.7.

The legacy features that are based on Information Server components are no longer available.

For more information about migrating, see Migrating and removing legacy governance features.

Determining the optional features to enable

You need to decide which optional features, if any, you want to enable for Watson Knowledge Catalog. These features are enabled through the Watson Knowledge Catalog custom resource (CR) during install or upgrade. For more information on how to enable these during install or upgrade, see Installing Watson Knowledge Catalog or Upgrading Watson Knowledge Catalog.

These optional features can also be enabled after the initial install or upgrade. If you decide to enable them after, see Enabling optional features after installation or upgrade for Watson Knowledge Catalog.

Use the following table to decide which optional features you would like to enable and find out which optional component you would need to enable that feature.
Table 1. Optional features and the component needed to enable
Feature Component needed Entry in the custom resource
Lineage Knowledge graph 
enableKnowledgeGraph: True
Semantic search Knowledge graph 
enableKnowledgeGraph: True
Data quality features Data quality 
enableDataQuality: True
Advanced metadata import MANTA Automated Data Lineage

For users on version 4.7.0, 4.7.1 and 4.7.2, you can enable MANTA Automated Data Lineage for Watson Knowledge Catalog.

For users on 4.7.3, MANTA Automated Data Lineage is installed and enabled separately from Watson Knowledge Catalog. For more information, see MANTA Automated Data Lineage.

 
enableMANTA: True

Configuring Db2 on a specific node

You can specify Db2® to run on specific nodes of your cluster. You might want to make this specification if, for example, your environment does not allow custom security context constraints (SCCs) to be deployed on certain nodes.

Important: You must complete this task when you create the Watson Knowledge Catalog custom resource (CR) at the time of installation. You cannot set these configurations after Watson Knowledge Catalog is installed.
  1. Create a custom machine configuration pool (MCP) by following the steps at Custom Machine Config Pool in OpenShift 4.
  2. Assign the KubeletConfig file to the node that you want by using the custom MCP.
  3. Label the node in the following format:
    oc label node <node> icp4data=<label>
    See the following example:
    oc label node worker1.newco-cpd.cp.ibm.com icp4data=wkcdb2u

    For more information, see Setting up dedicated nodes for your Db2 deployment.

  4. Skip this step until you have created the Watson Knowledge Catalog custom resource (CR) during the initial install process. Then, add the following override to the Watson Knowledge Catalog CR:
    spec:
 wkc_db2u_node_label: wkcdb2u
 iis_db2u_node_label: iisdb2u