By default, when Orchestrator deploys Gateway, it is exposed with LoadBalancer.
The exposure will be different when the Middleware is run in the Edge and different when it is run in the Cloud.
Based on the Middleware__InstanceType the gateway will be exposed in 2 different ways:
Cloud - LoadBalancer
Edge - NodePort (default NodePort 31000, user should be able to specify his own port)
On top of this, we need to take into consideration the presence of the CertManager and the Ingress Controller.
When the Ingress controller is present we will expose Gateway with ClusterIP.
Additional consideration: Think about configuring the Middleware using ConfigMap.
By default, when Orchestrator deploys Gateway, it is exposed with LoadBalancer. The exposure will be different when the Middleware is run in the Edge and different when it is run in the Cloud. Based on the
Middleware__InstanceTypethe gateway will be exposed in 2 different ways:LoadBalancerNodePort(default NodePort31000, user should be able to specify his own port)On top of this, we need to take into consideration the presence of the CertManager and the Ingress Controller. When the Ingress controller is present we will expose Gateway with
ClusterIP.Additional consideration: Think about configuring the Middleware using
ConfigMap.