In PPaaS, the backend members in the instances, such as in a Virtual Machine (VM) setup the VM instances and in a Kubernetes setup the Docker instances, are fronted by a Load Balancer. The proxyPort
property is used to define the port of the Load Balancer. When the Load Balancer receives traffic, it will route the traffic to the members (worker nodes) in the respective clusters, based on their resource availability.
...
Note |
---|
The URL to access a service depends on the port mapping (VM) and port range (Docker) that you defined in the cartridge definition and the Kubernetes cluster definition respectively. Expand |
---|
title | Click here for more information... |
---|
| When creating the dependent artifacts that are needed to deploy an application, you need to define port mapping in the cartridge definition JSON for each port that is being used with the WSO2 product cartridge. The following examples illustrate how to set unique proxy ports for each port that is used with the cartridge. Localtabgroup |
---|
Localtab |
---|
| Code Block |
---|
title | Example for defining proxy ports in the cartridge definition |
---|
| "portMapping": [
{
"name": "mgt-http",
"protocol": "http",
"port": 9763,
"proxyPort": 80
},
{
"name": "mgt-https",
"protocol": "https",
"port": 9443,
"proxyPort": 443
}
], |
|
Localtab |
---|
| Code Block |
---|
title | Example for defining proxy ports in the Cartridge definition |
---|
| "portMapping": [
{
"name": "mgt-http",
"protocol": "http",
"port": 9763,
"proxyPort": 0,
"kubernetesPortType": "NodePort"
},
{
"name": "mgt-https",
"protocol": "https",
"port": 9443,
"proxyPort": 0,
"kubernetesPortType": "NodePort"
}
], |
Code Block |
---|
title | Defining the portRange in the Kubernetes cluster definition |
---|
| "portRange": {
"upper": "32767",
"lower": "30000"
}, |
|
|
|
|
...