So, by now youâ€™re probably wondering â€“ what about this whole multi-cloud deployment thing the API Connect team has been raving about?Â How can I deploy API Connect 2018.x anywhere I want, in just about any configuration that I wish?
The answer: API Connect 2018.x for Containers.
Containers: lightweight, stand-alone, executable package that includes everything needed to run a piece of software
Docker: tool designed to make it easier to create, deploy, and run applications through the use of containers
Kubernetes: container arrangement system that automates container operations
I like to think of Containers, Docker, and Kubernetes as components of an orchestra.Â Containers are the musicians â€“ without them no music is produced (no application is run) because the core component of the orchestra is missing.Â Docker represents the various instruments in the orchestra.Â Docker is the tool needed to actually play the music — or run an application. Â Kubernetes is the conductor.Â It leads the orchestra, telling the musicians what and when to play.Â In the same way, Kubernetes allows you to arrange containers across different machines, scale up or scale down by adding or removing containers, distributing load between containers, and much much more.
The good news is that you can run Kubernetes and Docker containers pretty much anywhere.Â This is why we support running API Connect 2018.1 anywhere â€“ on premise or in the cloud.Â Not only can you deploy the different components of API Connect anywhere, but you can also co-locate Gateway components with your valuable data, scale different components at will, and do much more to enable success for both your business and the consumers of your APIs.
But first, hereâ€™s a bit more background.Â Our movement from a monolithic architecture to a microservice architecture changes things.Â Each microservice uses certificates to securely communicate with other microservices.Â Each microservice has certificates and configurations for deployment that can become quite difficult to manage as you scale.Â Deployment depends on the userâ€™s environment, so we cannot create a â€śone size fits allâ€ť solution to install the components of API Connect 2018.x for Containers.
Luckily, the API Connect team has created the pack mule that is InstallAssist.Â As a user, you load up InstallAssist with the necessary information based on your environment, and sit back as the pack mule does all the heavy lifting for you.Â InstallAssist is a binary that automatically manages certificate creation and configuration for deployment, so the heavy lifting with installation is done for you.Â InstallAssist (available as a Mac, Windows, or Linux download), as well as the Docker containers are provided by IBM.Â You just need to have your Kubernetes environment up and running with the minimum system requirements needed to run API Connect 2018.x.
So what do you need to do to deploy an API Manager component of APIC 2018.1 for Containers?Â The process is straightforward:
- Ensure your Kubernetes cluster meets the requirements for installation
- Download API Connect Container images and InstallAssist
- Input characteristics of your environment into the InstallAssist yaml file
- Run InstallAssist (and take a look at everything you donâ€™t have to do!)
- Start using API Connect!
The process for deploying Analytics and Developer Portal Containers follows a very similar process.Â For more information on installing DataPower in your environment, please visit our DataPower Knowledge Center here.
The API Connect team has created a walkthrough of the Container installation process.Â Please visit our API Connect Knowledge Center for a detailed walk through of individual steps for the Container installation.Â Please also visit the Software Product Compatibility Report page for detailed System Requirements of API Connect 2018.x.