Using Default Init Container Image
If you are installing or upgrading to Sterling B2B Integrator v6.2.0.0 or above, the resourcesInit section comes configured with the default out of the box resources init container image details.
The image comes bundled with the latest supported database driver versions, namely:
- Oracle - 21.6.0.0.0
- DB2 - 4.32.28
- MSSQL - 11.2.0
The configurations listed below are available to set up the default init
container for
resources:
# resourcesInit section to configure init container for external resources
resourcesInit:
# enabled can be set to true to configure resources init container
enabled: false
image:
# repository for the init container image
repository: "cp.icr.io/cp/ibm-b2bi"
# name for the init container image
name: "b2bi-resources"
# tag for the init container image. Optional if digest is provided.
tag: "6.2.0.0"
# digest for the init container image. Optional if tag is provided.
digest: sha256:660f8b8a48985d2981dc1bb31b9667aabfe4b8829221a8e48e64e3de01eaed08
# pullPolicy for the init container image
pullPolicy: "IfNotPresent"
# command to execute for the init container
command:
If all you need is the JDBC database driver, set
resourcesInit.enabled
to true and disable the
appResourcesPVC.enabled
flag by setting it to false.If you are using Sterling B2B Integrator v6.2.0.0 or above or if you want to provide your own resource container image, See Building Custom Init Container Image.