Creating an override file for Watson Discovery
An override file enables you to specify how Watson Discovery is installed on your environment.
You must create and use the override file if you want to enable the Content Intelligence feature
that is required for the Document Retrieval for Contracts project type to be available. You also
must specify the override file to install Watson Discovery in production mode.
Important: You cannot change the configuration of the deployed service by applying changes you
make to the override file after the initial installation. If you want to make a change, you must
uninstall and reinstall the service. Be sure to review and choose the right values for the override
file before you install the service.
The override file for Watson Discovery must be written in YAML, created in a location
accessible from the cpd-cli
command that is used to install Watson Discovery,
and the user executing the command must have read access to the file. Perform the following steps to
create the override file:
- Create a file with an appropriate name. For example
discovery-override.yaml
- Add the following text as the first line of the file:
wdRelease:
- Add any override options that you want to use in subsequent lines that are indented. The
available options include these values:
- deploymentType
- The
Development
deployment type is used by default. To enable production mode, set this value toProduction
. Use an uppercase P. - enableContentIntelligence
- Content Intelligence features are not enabled by default. To enable the Content Intelligence
features, set this value to
true
.
- If you want to specify different values for the persistent volume claim (PVC) storage request
size of the data stores, you can do so by adding the following values and specifying corresponding sizes.
- elasticsearch.clientNode.persistence.persistence.size
- Persistent volume claim size for the Elasticsearch client node. The default size is
1Gi
. - elasticsearch.dataNode.persistence.persistence.size
- Persistent volume claim size for the Elasticsearch client node. The default size is
40Gi
. - elasticsearch.masterNode.persistence.persistence.size
- Persistent volume claim size for the Elasticsearch coordinator node. The default size is
2Gi
. - etcd.storageSize
- Persistent volume claim size for etcd data store. The default size is
10Gi
. - minio.persistence.size
- Persistent volume claim size for the MinIO data store. The default size is
100Gi
. - postgres.database.storageRequest
- Persistent volume claim size for the PostgreSQL database. The default size is
30Gi
. - rabbitmq.persistentVolume.size
- Persistent volume claim size for the RabbitMQ data store. The default size is
5Gi
.
The following example illustrates the syntax of the file. The example shows and override file for
a production deployment with the Content Intelligence feature enabled. The override file also
changes the storage size for Etcd from 10 Gi to 15 Gi and for PostgreSQL from 30 Gi to 50
Gi.
wdRelease:
deploymentType: Production
enableContentIntelligence: true
etcd:
storageSize: 15Gi
postgres:
database:
storageRequest: 50Gi
Next Steps
Install the service using the override: Installing Watson Discovery