CODEWITHSUNDEEP
wso2wso2-api-manager
peter
peter

Reputation: 117

WSO2 API manager with Kubenetes deployed back end services

I am thinking of deploying the WSO2 API manager/GW in VM's (Not in kubernetes) and forwarding all API calls to a nginx ingress controller running in my kubernetes cluster which also has all the back end services that expose API's. I could not find any info on the documentation for deployment like this and wanted to check if this has any known pitfalls.

Upvotes: 0

Views: 120

Answers (1)

Pubci
Pubci

Reputation: 4001

This is doable and acceptable. For API Manager gateways, your backend services look like just another endpoint. When you are creating an API in the API publisher you can create an API and provide the ingress URL for your backend service. If the gateway can access the ingress gateway, you should be able to invoke the API successfully. Only drawback in this approach is network latency.

If you deploy the API manager in K8s, then you can drop this network latency as you can access the backend services via the services in K8s. If you do not have any concern with the latency, you can follow this approach. I have seen this pattern in the industry and people are using this approach.

If you want to deploy API Manager in K8s, you can check https://github.com/wso2/kubernetes-apim

Upvotes: 0

Related Questions