Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
..
Failed to load latest commit information.
LICENSES
templates
.helmignore
Chart.yaml
LICENSE
README.md
RELEASENOTES.md
values-metadata.yaml
values.yaml

README.md

IBM DataPower Gateway

IDG Logo

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.

Introduction

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.

Prerequisites

helm and kubectl must be installed and configured on your system.

Resources Required

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

Where <mycrypto.yaml> is a yaml file that contains the parameters crypto.frontsideCert and 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 helm list

Verifying the Chart

See NOTES.txt associated with this chart for verification instructions

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

To completely uninstall/delete the my-release deployment:

$ helm delete --purge my-release

Limitations

This chart is for developer purposes only. No support is provided. Not eligible for production use.

Chart Details

Deploys IBM DataPower Gateway Virtual Edition for Developers. Only works with DataPower version 7.7.1.1 and above.

Configuration

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

Value Description Default
datapower.replicaCount The replicaCount for the deployment 1
datapower.image.repository The image to use for this deployment ibmcom/datapower
datapower.image.tag The image tag to use for this deployment latest
datapower.image.pullPolicy Determines when the image should be pulled IfNotPresent
datapower.image.pullSecrets Range of kubernetes pull secrets N/A
datapower.env.workerThreads Number of DataPower worker threads 4
datapower.resources.limits.cpu Container CPU limit 8
datapower.resources.limits.memory Container memory limit 64Gi
datapower.resources.requests.cpu Container CPU requested 4
datapower.resources.requests.memory Container Memory requested 8Gi
datapower.webGuiManagementState WebGUI Management admin state disabled
datapower.webGuiManagementPort WebGUI Management port 9090
datapower.gatewaySshState SSH admin state disabled
datapower.gatewaySshPort SSH Port 9022
datapower.restManagementState REST Management admin state disabled
datapower.restManagementPort REST Management port 5554
datapower.xmlManagementState XML Management admin state disabled
datapower.xmlManagementPort XML Management port 5550
datapower.snmpState SNMP admin state enabled
datapower.snmpPort SNMP interface port 1161
service.name Name to add to service datapower
patternName The name of the datapower pattern to load RESTProxy
RESTProxy.backendURL The backend URL datapower will proxy https://www.ibm.com
RESTProxy.containerPort The backend URL datapower will proxy 8443
crypto.frontsideCert base64 encoded certificate N/A
crypto.frontsideKey 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

The 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.containerPort and proxies to RESTProxy.backendURL.
  • none : Does not include any configuration. You may only interact with the gateway using kubectl attach.

Tip: You can use the default values.yaml

View the official IBM DataPower Gateway for Developers Docker Image in Docker Hub

View the IBM DataPower Gateway Product Page

View the IBM DataPower Gateway Documentation

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.