scenario-12

Scenario-12 : Deploy API Manager Pattern-3

Installation Prerequisiyes

• NGINX Ingress Controller.

In this scenario we are deploying API Manager Pattern-3 by using the following simple yaml definition. All API Manager servers are exposed via Ingress Controller.

apiVersion: apim.wso2.com/v1alpha1
kind: APIManager
metadata:
  name: cluster-1
spec:
  pattern: Pattern-3

---

Deploy pattern 3

kubectl create -f wso2-apim.yaml

Access API Manager

Get the external address of the ingresses using the command,

kubectl get ing

Output:
NAME                                   HOSTS                    ADDRESS         PORTS      AGE
wso2-am-analytics-dashboard-ingress    analytics.am.wso2.com    34.67.188.5     80, 443    36m
wso2-am-devportal-ingress              devportal.am.wso2.com    34.67.188.5     80, 443    36m
wso2-am-gw-ingress                     gateway.am.wso2.com      34.67.188.5     80, 443    36m
wso2-am-publisher-ingress              publisher.am.wso2.com    34.67.188.5     80, 443    36m

Add an /etc/hosts/ entry as follows.

/etc/hosts
- - - - - - - - - - 
<EXTERNAL-ADDRESS>       analytics.am.wso2.com gateway.am.wso2.com publisher.am.wso2.com devportal.am.wso2.com

• API Publisher : https://publisher.am.wso2.com
• API Devportal : https://devportal.am.wso2.com
• API Analytics Dashboard : https://analytics.am.wso2.com
• API Gateway : https://gateway.am.wso2.com