The API Gateway team is working on the implementation of ephemeral Gateway deployment on Kubernetes. As part of this effort, we’re developing the capability to deploy Helm charts, which will allow our customers to simply deploy their Gateway in an efficient manner and give ownership of Gateway scaling, health checks and rollbacks to the Kubernetes cluster.
The reference implementation will be distributed as Helm charts and this post explains what Helm and Helm Charts are, and how we can use these charts to deploy the Gateway on Kubernetes.
What is Helm and Helm Charts?
Helm is a package manager tool used for installing and managing Kubernetes applications. These Helm packages are what is known as Helm Charts. Helm Charts consists of a collection of files that are rendered into Kubernetes manifest files and allows the users to deploy applications, services, and tools from a template.
- Helm installed
- Valid License for the API Gateway
Configurations and Deployment of the Gateway
The Gateway can be deployed by using the Helm chart, which can be found attached to this post. After unzipping the file, follow the instructions in the README.md file to correctly deploy your gateway on to the Kubernetes cluster. The chart templates serves as base templates which you can configure in the values.yaml file. The README.md file explains what each variable is used for and how to set files and variables as required.
Note that this particular Helm chart-driven deployment is for a base standalone Gateway (built with the Gateway Version 9.4.00 image) using an embedded Apache Derby database .
While there currently isn’t a way to apply a bundle with the Helm charts, you can instead bake the bundle into the Gateway image by using a Dockerfile OR use RESTman to import bundles after your Gateway has started running.
Stay tuned for further updates on our progress with the ephemeral Gateway deployment on Kubernetes!