

Deploying Choreo Connect on Kubernetes With WSO2 API Manager as a Control Plane¶

Let's deploy an API on Choreo Connect, which running on Kubernetes, with WSO2 API Manager as the Control Plane.

Before you begin¶

Install kubectl.
Set up a Kubernetes cluster v1.20 or above.
- Minimum CPU : 4vCPU
- Minimum Memory : 3GB
Deploy an ingress controller - NGINX Ingress Controller for this sample.

Note

If you are using Rancher Desktop, disable the default Traefik ingress controller in order to deploy the Nginx ingress controller.

Refer Rancher Docs for more information

Let's get started...

Download and extract Choreo Connect distribution .zip file

Latest Choreo Connect distribution can be downloaded from https://wso2.com/choreo/choreo-connect/. Extract the Choreo Connect distribution .zip file. The extracted folder will be called as CHOREO-CONNECT_HOME hereafter.

Add the Kubernetes configurations for Choreo Connect and API Manager using the kubectl tool.

Click here if you are using an ARM64 based machine (e.g., Apple M1)

If you are trying out in ARM64 based machine (e.g., Apple M1) update the Docker image names with the following in

Existing (Default) image name	Image name for tryout in ARM64 (e.g.: Apple M1)
wso2/choreo-connect-adapter:1.0.0	wso2/choreo-connect-adapter:1.0.0-ubuntu
wso2/choreo-connect-enforcer:1.0.0	wso2/choreo-connect-enforcer:1.0.0-ubuntu
wso2/choreo-connect-router:1.0.0	wso2/choreo-connect-router:1.0.0-ubuntu
wso2/wso2am:4.0.0-alpine	wso2am/wso2am:4.0.0-ubuntu

Note:
Note that the above Ubuntu based (*-ubuntu) images are for tryout purpose only, not recommended for a production deployment.

kubectl apply -f <CHOREO-CONNECT_HOME>/k8s-artifacts/choreo-connect-with-apim/apim

Apply Kubernetes configurations for Choreo Connect after successfully started the API Manager instance.

kubectl apply -f <CHOREO-CONNECT_HOME>/k8s-artifacts/choreo-connect-with-apim/choreo-connect

Top