Page Comparison

...

Note

Anchor

	pre
	pre

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

active	true
title	EC2

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

title	Kubernetes

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"
    },

...

Versions Compared

Old Version 13

New Version 14

Key