Skip to content
This repository was archived by the owner on Oct 5, 2021. It is now read-only.

Proxy Port Range Used for Kubernetes and Mesos Platforms

Thanuja Uruththirakodeeswaran edited this page Jul 28, 2016 · 2 revisions

In Kubernetes and Mesos platforms, proxy ports for various exposed ports (e.g., Servlet HTTP & HTTPS, Pass-Through HTTP & HTTPS) are assigned according to the following ranges, which are allocated to each product. These port ranges and the proxy port values, which are in the YAML files in the Kubernetes/Mesos platform, match the ports allocated as NodePorts/ServicePorts in the Kubernetes Services/ Mesos Marathon applications of the respective product in the wso2/kubernetes-artifacts and wso2/mesos-artifacts repository respectively. Therefore, the Kubernetes and the Mesos platform YAML files work out-of-the-box with the Kubernetes and Mesos Artifacts provided by wso2/kubernetes-artifacts and wso2/mesos-artifacts.

Product Kubernetes NodePort range Mesos ServicePort range
WSO2AM 32000 - 32020 10151 - 10175
WSO2AS 32021 - 32030 10021 - 10030
WSO2BPS 32031 - 32040 10031 - 10040
WSO2BRS 32041 - 32050 10041 - 10050
WSO2CEP 32051 - 32060 10051 - 10060
WSO2DAS 32061 - 32070 10061 - 10070, 10176 - 10185
WSO2DSS 32071 - 32080 10071 - 10080
WSO2ES 32081 - 32090 10081 - 10090
WSO2ESB 32091 - 32100 10091 - 10100
WSO2GREG 32101 - 32110 10101 - 10110
WSO2IS 32111 - 32120 10111 - 10120
WSO2MB 32121 - 32130 10121 - 10130
WSO2GREG_PUBSTORE 32131 - 32140 10131 - 10140
WSO2IS_KM 32141 - 32150 10141 - 10150