Installing IBM Knowledge Catalog
An instance administrator can install IBM Knowledge Catalog on IBM® Software Hub Version 5.2.
- Who needs to complete this task?
-
Instance administrator To install IBM Knowledge Catalog, you must be an instance administrator. An instance administrator has permission to install software in the following projects:
- The operators project for the instance
-
The operators for this instance of IBM Knowledge Catalog are installed in the operators project.
In the installation commands, the
${PROJECT_CPD_INST_OPERATORS}environment variable refers to the operators project. - The operands project for the instance
-
The custom resources for the control plane and IBM Knowledge Catalog are installed in the operands project.
In the installation commands, the
${PROJECT_CPD_INST_OPERANDS}environment variable refers to the operands project.
- When do you need to complete this task?
-
Review the following options to determine whether you need to complete this task:
- If you want to install multiple services at the same time, follow the process in Running a batch installation of solutions and services instead.
- If you didn't install IBM Knowledge
Catalog as part of a batch installation, complete this task
to add IBM Knowledge
Catalog to your environment.
Repeat as needed If you are responsible for multiple instances of IBM Software Hub, you can repeat this task to install more instances of IBM Knowledge Catalog on the cluster.
Information you need to complete this task
Review the following information before you install IBM Knowledge Catalog:
- Version requirements
-
All of the components that are associated with an instance of IBM Software Hub must be installed at the same release. For example, if the IBM Software Hub control plane is installed at Version 5.2.2, you must install IBM Knowledge Catalog at Version 5.2.2.
- Environment variables
-
The commands in this task use environment variables so that you can run the commands exactly as written.
- If you don't have the script that defines the environment variables, see Setting up installation environment variables.
- To use the environment variables from the script, you must source the environment variables
before you run the commands in this task. For example,
run:
source ./cpd_vars.sh
- Security context constraint
-
IBM Knowledge Catalog works with the default Red Hat® OpenShift® Container Platform security context constraint,
restricted-v2.
- Common core services
-
IBM Knowledge Catalog requires the IBM Software Hub common core services.
If the common core services are not installed in the operands project for the instance, the common core services are automatically installed when you install IBM Knowledge Catalog. The common core services installation increases the amount of time the installation takes to complete.
- Storage requirements
- You must specify storage classes when you install IBM Knowledge Catalog. The following storage classes are recommended. However, if you don't use these storage classes on your cluster, ensure that you specify a storage class with an equivalent definition.
Before you begin
This task assumes that the following prerequisites are met:
- System requirements
- This task assumes that the cluster meets the minimum requirements for IBM Knowledge
Catalog.
Where to find more information If this task is not complete, see System requirements. - Workstation
- This task assumes that the workstation from which you will run the installation is set up as a
client workstation and has the following command-line interfaces:
- IBM Software Hub CLI:
cpd-cli - OpenShift CLI:
oc
Where to find more information If this task is not complete, see Setting up a client workstation. - IBM Software Hub CLI:
- Control plane
- This task assumes that the IBM Software Hub
control plane is installed.
Where to find more information If this task is not complete, see Installing an instance of IBM Software Hub. - Private container registry
- If your environment uses a private container registry (for example, your cluster is air-gapped),
this task assumes that the following tasks are complete:
- The IBM Knowledge
Catalog software images are mirrored to the private container
registry.
Where to find more information If this task is not complete, see Mirroring images to a private container registry. - The
cpd-cliis configured to pull theolm-utils-v3image from the private container registry.Where to find more information If this task is not complete, see Pulling the olm-utils-v3 image from the private container registry.
- The IBM Knowledge
Catalog software images are mirrored to the private container
registry.
- Load balancer
- The load balancer timeout settings are adjusted for IBM Knowledge
Catalog.
Where to find more information If this task is not complete, see Changing load balancer settings. - GPU operators
- If you plan to use
features that require GPUs, this task assumes that the operators required to use GPUs are
installed.
Where to find more information If this task is not complete, see Installing operators for services that require GPUs.
Procedure
Complete the following tasks to install IBM Knowledge Catalog:
Specifying your IBM Knowledge Catalog edition
IBM Knowledge Catalog is available in three different editions. You must specify which edition to install.
Set the IKC_TYPE environment variable to the edition of IBM Knowledge
Catalog
that you want to install:
- IBM Knowledge Catalog
-
export IKC_TYPE=wkc - IBM Knowledge Catalog Premium
-
export IKC_TYPE=ikc_premium - IBM Knowledge Catalog Standard
-
export IKC_TYPE=ikc_standard
Specifying installation options
If you plan to install IBM Knowledge Catalog, IBM Knowledge Catalog Premium, or IBM Knowledge Catalog Standard, you can specify installation
options in a file named install-options.yml in the
cpd-cli
work directory (For example: cpd-cli-workspace/olm-utils-workspace/work).
The parameters are optional. If you do not set these installation parameters, the default values are used. Uncomment the parameters that you want to override and update the values appropriately.
The applicable parameters and default values depend on which service you install:
- IBM Knowledge Catalog
-
The sample YAML content uses the default values.
################################################################################ # IBM Knowledge Catalog parameters ################################################################################ custom_spec: wkc: # enableDataQuality: False # enableKnowledgeGraph: False # useFDB: False - IBM Knowledge Catalog Premium
-
The sample YAML content uses the default values.
################################################################################ # IBM Knowledge Catalog parameters ################################################################################ custom_spec: wkc: # enableDataQuality: False # enableKnowledgeGraph: False # useFDB: False # enableAISearch: False # enableSemanticAutomation: False # enableSemanticEnrichment: True # enableSemanticEmbedding: False # enableTextToSql: False # enableModelsOn: 'cpu' # customModelTextToSQL: granite-3-3-8b-instruct - IBM Knowledge Catalog Standard
-
The sample YAML content uses the default values.
################################################################################ # IBM Knowledge Catalog parameters ################################################################################ custom_spec: wkc: # enableKnowledgeGraph: False # useFDB: False # enableAISearch: False # enableSemanticAutomation: False # enableSemanticEnrichment: True # enableSemanticEmbedding: False # enableTextToSql: False # enableModelsOn: 'cpu' # customModelTextToSQL: granite-3-3-8b-instruct
| Property | Description |
|---|---|
enableDataQuality |
Specify whether to enable data quality features in projects. Important: If you
enable this feature, DataStage, specifically DataStage Enterprise, is automatically installed.
If you did not purchase a DataStage license, use of DataStage Enterprise is limited to creating, managing, and running data quality rules. For examples of accepted use, see Enabling optional features after installation or upgrade for IBM Knowledge Catalog.
|
enableKnowledgeGraph |
Specify whether to enable the knowledge graph feature. The knowledge graph provides the
following capabilities:
|
useFDB |
Specify which database to use to store the data generated by knowledge graph. The
database depends on which service you use for lineage:
|
enableAISearch |
Specify whether to enable LLM-based semantic search for assets and artifacts across all workspaces.
|
enableSemanticAutomation |
Specify whether to enable gen AI features.
|
enableSemanticEnrichment |
Specify whether to enable gen AI metadata expansion. Metadata expansion includes:
|
enableSemanticEmbedding |
5.2.1 and later This parameter is available starting in IBM Software Hub Version 5.2.1. Specify whether to enable semantic embedding. You must enable semantic embedding if you plan to use the following features:
|
enableTextToSql |
5.2.1 and later This parameter is available starting in IBM Software Hub Version 5.2.1. Specify whether to generate SQL queries from natural language input. Text-to-SQL capabilities can be used to create query-based data assets, which can be use for data products or in searches.
|
enableModelsOn |
Specify where you want the models that are used with the gen AI capabilities to run.
|
customModelTextToSql |
Specify a custom model for Text-To-SQL conversions.
|
Installing the service
To install IBM Knowledge Catalog:
-
Log the
cpd-cliin to the Red Hat OpenShift Container Platform cluster:${CPDM_OC_LOGIN}Remember:CPDM_OC_LOGINis an alias for thecpd-cli manage login-to-ocpcommand. - Run the following command to create the required OLM objects for IBM Knowledge
Catalog in the
operators project for the
instance:
cpd-cli manage apply-olm \ --release=${VERSION} \ --cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \ --components=${IKC_TYPE}Wait for thecpd-clito return the following message before you proceed to the next step:[SUCCESS]... The apply-olm command ran successfullyIf the
apply-olmfails, see Troubleshooting the apply-olm command during installation or upgrade. - Create the custom resource for IBM Knowledge
Catalog.
The command that you run depends on the storage on your cluster.
Red Hat OpenShift Data Foundation storage
Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
IBM Fusion Data Foundation storage
Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
IBM Fusion Global Data Platform storage
Remember: When you use IBM Fusion Global Data Platform storage, both${STG_CLASS_BLOCK}and${STG_CLASS_FILE}point to the same storage class, typicallyibm-spectrum-scale-scoribm-storage-fusion-cp-sc.Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
IBM Storage Scale Container Native storage
Remember: When you use IBM Storage Scale Container Native storage, both${STG_CLASS_BLOCK}and${STG_CLASS_FILE}point to the same storage class, typicallyibm-spectrum-scale-sc.Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
Portworx storage
Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --storage_vendor=portworx \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --storage_vendor=portworx \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
NFS storage
Remember: When you use NFS storage, both${STG_CLASS_BLOCK}and${STG_CLASS_FILE}point to the same storage class, typicallymanaged-nfs-storage.Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
AWS with EFS storage only
Remember: When you use EFS storage, both${STG_CLASS_BLOCK}and${STG_CLASS_FILE}point to the same storage class, typicallyefs-nfs-client.Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
AWS with EFS and EBS storage
Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
NetApp Trident
Remember: When you use NetApp Trident storage, both${STG_CLASS_BLOCK}and${STG_CLASS_FILE}point to the same storage class, typicallyontap-nas.Run the appropriate command to create the custom resource.
- Default installation (without installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --license_acceptance=true - Custom installation (with installation options)
-
cpd-cli manage apply-cr \ --components=${IKC_TYPE} \ --release=${VERSION} \ --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \ --block_storage_class=${STG_CLASS_BLOCK} \ --file_storage_class=${STG_CLASS_FILE} \ --param-file=/tmp/work/install-options.yml \ --license_acceptance=true
Validating the installation
apply-cr command
returns:[SUCCESS]... The apply-cr command ran successfully
If you want to confirm that the custom resource status is
Completed, you can run the cpd-cli
manage
get-cr-status command:
cpd-cli manage get-cr-status \
--cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} \
--components=${IKC_TYPE}
What to do next
Your next steps depend on the version of IBM Software Hub that you installed:
- Version 5.2.1 or later
-
After you complete the preceding steps, IBM Knowledge Catalog is ready to use.
- Version 5.2.0
-
- Install the services that you need on this instance of IBM Software Hub
- Apply the IBM Software Hub Version 5.2.0 - Day 0 patch
You must apply the patch to each instance of IBM Software Hub Version 5.2.0 that you install.
After you complete the preceding steps, IBM Knowledge Catalog is ready to use.