Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Network Plugin 


Ingresses require an Ingress Controller to work. The Ingress Controller takes care of applying the routing rule defined in the Ingress resources as well as routing the incoming traffic to the correct backing Service. The backing service does not have to be exposed outside of the cluster since the Ingress Controller exposes its own port, usually through a NodePort. Usage Engine comes with a preconfigured Nginx Ingress Controller. The use of that is optional and it works perfectly fine to replace Nginx with another Ingress Controller, as needed. 

Usage Engine and Network Resources 

An overview of how networking resources can be used by Usage Engine is illustrated below. Note that this is only an example, and that this can depending on the implemented solution and on cloud environment specifics. 

Usage Engine and Network Resources

We distinguish between network of the Usage Engine platform itself and the solutions implemented on it using ECDs. Note that there is no built-in network level separation on traffic between these kinds of network traffic, although it is possible to achieve this through configuration in the environment 


The Usage Engine platform and web backend processes need to expose ports to enable access to REST APIs. To connect an external Desktop client also TCP level access, need to be exposed. 

The ports are: 

Pod Port 

Cluster Port 

Used for 



platform:80 or  

Operational APIs  
Desktop client authentication 




Desktop control interface 




Web Desktop - Web UI 




DROnline - Web UI 


 The ports in the table are by default exposed as NodePorts, but this can be changed during installation.