Latest revision as of 18:26, 12 March 2026

When deploying IBM Connect:Direct in Kubernetes environments, administrators may need to augment the container with additional storage locations for configuration files, scripts, logs, key stores, partner‑exchange directories, or other operational assets.

To support this requirement, the Connect:Direct deployment architecture includes two extensible configuration fields:

extraVolume
extraVolumeMounts

These fields allow users to define and mount additional hostPath or persistent volumes into the Connect:Direct container without modifying the base container image, maintaining flexibility and portability.

extraVolume Definition

extraVolume:
  - name: svshare-volume
    hostPath:
      path: /svshare
      type: Directory

  - name: backup-volume
    nfs:
      path: <nfs data path>
      server: <server ip>

extraVolumeMounts Definition

extraVolumeMounts:
  - name: svshare-volume
    mountPath: /svshare

  # Replace BACKUP (/opt/backup)
  - name: backup-volume
    mountPath: /opt/backup

Ver também

Artigos sobre IBM Sterling

@@ Line 7: / Line 7: @@
 These fields allow users to define and mount additional hostPath or persistent volumes into the Connect:Direct container '''without modifying the base container image''', maintaining flexibility and portability.
-= Sample Configuration =
-Below is a complete example showing how to define and mount two custom volumes: one backed by a local host path and another backed by NFS.
 == extraVolume Definition ==