IBM DataPower Gateway
IBM® DataPower Gateway is a purpose-built security and integration gateway that addresses the business needs for mobile, API, web, SOA, B2B, and cloud workloads. It is designed to provide a consistent configuration-based approach to security, governance, integration and routing.
This chart deploys a single IBM DataPower Gateway node with a default pattern into an IBM Cloud Private or other Kubernetes environment. The default pattern, the
RESTProxy pattern, configures the DataPower node to act as a reverse proxy, directing client requests to the appropriate backend server.
helm and kubectl must be installed and configured on your system.
Minimum resources per pod: 2 CPU and 4 GB RAM
Installing the Chart
To install the chart with the release name
my-release and default pattern (See .Values.patternName below):
$ helm install --name my-release -f <mycrypto.yaml> stable/ibm-datapower-dev
<mycrypto.yaml> is a yaml file that contains the parameters
crypto.frontsideKey and their respective base64-encoded values. These values are the base64-encoding of the raw key and certificate file with all whitespace removed.
Tip: List all releases using
Verifying the Chart
See NOTES.txt associated with this chart for verification instructions
Uninstalling the Chart
To uninstall/delete the
$ helm delete my-release
To completely uninstall/delete the
$ helm delete --purge my-release
This chart is for developer purposes only. No support is provided. Not eligible for production use.
Deploys IBM DataPower Gateway Virtual Edition for Developers. Only works with DataPower version 22.214.171.124 and above.
The helm chart has the following Values that can be overriden using the install
--set parameter or by providing your own values file. For example:
helm install --set image.repository=<myimage> stable/ibm-datapower-dev
||The replicaCount for the deployment||1|
||The image to use for this deployment||ibmcom/datapower|
||The image tag to use for this deployment||latest|
||Determines when the image should be pulled||IfNotPresent|
||Range of kubernetes pull secrets||N/A|
||Number of DataPower worker threads||4|
||Container CPU limit||8|
||Container memory limit||64Gi|
||Container CPU requested||4|
||Container Memory requested||8Gi|
||WebGUI Management admin state||disabled|
||WebGUI Management port||9090|
||SSH admin state||disabled|
||REST Management admin state||disabled|
||REST Management port||5554|
||XML Management admin state||disabled|
||XML Management port||5550|
||SNMP admin state||enabled|
||SNMP interface port||1161|
||Name to add to service||datapower|
||The name of the datapower pattern to load||RESTProxy|
||The backend URL datapower will proxy||https://www.ibm.com|
||The backend URL datapower will proxy||8443|
||base64 encoded certificate||N/A|
||base64 encoded key||N/A|
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
$ helm install --name my-release -f values.yaml stable/ibm-datapower-dev
patternName specifies the configuration included with the deployment. Pattern-specific options are prefixed by the
patternName in values.yaml.
The available patterns are:
RESTProxy: Configures the DataPower Gateway as a proxy for RESTful services, the service is available over HTTP or HTTPS(if crypto parameters are set) at
RESTProxy.containerPortand proxies to
none: Does not include any configuration. You may only interact with the gateway using
Tip: You can use the default values.yaml
Copyright© IBM Corporation 2017. All Rights Reserved.
The IBM DataPower Gateway logo is copyright IBM and is provided for use for the purposes of IBM Cloud Private. You will not use the IBM DataPower Gateway logo in any way that would diminish the IBM or IBM DataPower Gateway image. IBM reserves the right to end your privilege to use the logo at any time in the future at our sole discretion. Any use of the IBM DataPower Gateway logo affirms that you agree to adhere to these conditions.