Skip to main content

Advanced Configuration

Overview​

This page gives details on advanced BDI configuration. This involves making direct modifications to the ManageWorkspace custom resource (CR) by an Open Shift administrator.

Manage Custom Resource Settings​

Two BDI settings can be configured by updating (or patching) the "bdiConfigurations" section of the ManageWorkspace Custom Resource.

SettingDescription
imagePullPolicyDetermines when the BDI image will be retrieved from the IBM Entitled Registry.
By default the value is: IfNotPresent.
This setting is mainly used for internal development purposes.
enableRoute:Determines whether an external Route is created, by the BDI entity manager, to the BDI OpenShift service.
An external route can be useful for examining the BDI API documentation (Swagger docs) or making BDI API calls from an external system.
A valid MAS 'x-access-token' cookie is required for external BDI requests.
The default is for the Route to be enabled.

Because the "bdiConfigurations" property of the ManageWorkspace custom resource is recorded in an Array it is recommended to update the yaml definition directly in the Open Shift console if modifying any of these additional properties. If an OC patch command is used to update the bdiConfigurations section of the ManageWorkspace Custom Resource then all of the properties in the bdiConfiguration array element must be specified. This is a limitation of the Kubernetes patch command.

BDI Workload Customization​

The ManageWorkspace custom resource spec.components.acm can be updated to specify BDI container pod templates.
For example to override the resources for the BDI Instance "bdi-1" the following yaml is specified:

spec:
bindings:
jdbc: workspace-application
components:
acm:
podTemplates:
- containers:
- name: bdiservice
resources:
limits:
cpu: 3
memory: 8Gi
requests:
cpu: 1
memory: 1Gi
name: bdi-1
replicas: 1

Disabling the BDI pod​

The BDI pod can be disabled completed by setting the replicas property to zero:

spec:
bindings:
jdbc: workspace-application
components:
acm:
podTemplates:
- containers:
- name: bdiservice
name: bdi-1
replicas: 0

Support podTemplates​

The following podTemplates fields are supported:

  • replicas
  • resources
  • affinity
  • tolerations
  • securityContext
  • nodeSelector
  • topologySpreadConstraints