Using the Container Gateway
The Container Gateway form factor allows the gateway to be deployed in a PaaS environment as an industry-standard container.
The Container Gateway replaces the "Gateway Docker Appliance" that was available prior to version 9.3.
Gateway System Requirements
Prior to building and deploying your Container Gateway solution in a production environment, make sure you have the following basic prerequisites:
- A license XML file for yourLayer7 API Gateway
- A computer with at least 8GB of RAM
- A high-speed Internet connection (initial download is about 1GB in size)
- Access to the Docker image. The Container Gateway docker image can be obtained from caapim/gateway.
If you obtained the Gateway Docker image from a local Registry server (not the Docker Hub), contact your Registry server administrator for credentials.
If you are a PLA customer, you must configure the telemetry-related environment variables to satisfy the PLA agreement - to learn more, see Product Licensing and Telemetry.
Container Platform Overview
To see the latest versions of the container platforms that are currently supported by the
Layer7 API Gateway, see Container Gateway Platform Support.
Container Gateways Deployed with Kubernetes
The configuration and operation information contained in this documentation set describes how the
Layer7 API Gatewaycan be deployed with Kubernetes Engine. Kubernetes is an open source container orchestration system deploy and manage your Container Gateway in pods, that is, groups of one or more containers that run in a shared context. To successfully deploy the Container Gateway in GKE, the following tools or components are recommended:
While much of the Layer7 documentation focuses on a GKE deployment as a reference implementation, you can easily extend the same principles to OpenShift Origin, which is built upon GKE and Docker containers; the Container Gateway can also run in an OpenShift Origin or Docker-native environment using these tools or components: