IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments: Difference between revisions

From Wiki
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Using `extraVolume` and `extraVolumeMounts` in IBM Connect:Direct Deployments =
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.
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.


Line 12: Line 8:
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.
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.


== Purpose of `extraVolume` and `extraVolumeMounts` ==
== extraVolume Definition ==
The two fields work together as follows:
 
* '''extraVolume''' – Defines additional Kubernetes volumes—such as hostPath, NFS, emptyDir, or PVC references—that should be attached to the pod.
* '''extraVolumeMounts''' – Specifies where inside the Connect:Direct container each extra volume should be mounted.
 
This modular approach enables administrators to expand storage mappings in a controlled and repeatable way.
 
== Default Volume Mount Example ==
The deployment may include a default mount (as illustrated in the documentation), but additional volumes can be layered using these fields.
 
== 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 ===
<syntaxhighlight lang="yaml">
<syntaxhighlight lang="yaml">
extraVolume:
extraVolume:
Line 40: Line 22:
</syntaxhighlight>
</syntaxhighlight>


=== extraVolumeMounts Definition ===
== extraVolumeMounts Definition ==
<syntaxhighlight lang="yaml">
<syntaxhighlight lang="yaml">
extraVolumeMounts:
extraVolumeMounts:

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

Retrieved from "https://ebasso.net/wiki/index.php?title=IBM_Sterling_Connect:Direct:_Using_extraVolume_and_extraVolumeMounts_in_IBM_Connect:Direct_Deployments&oldid=9905"