Exposing ENBUILD UI

Introduction:

In production Kubernetes environments, exposing the ENBUILD UI service requires careful consideration to ensure accessibility and security. While the Quick install of ENBUILD facilitates local testing through port forwarding, deploying in a production scenario demands a more robust approach. This document outlines various options available for exposing the ENBUILD UI service outside the Kubernetes cluster.

Option 1: Expose UI using Kubernetes Service Type LoadBalancer#

Setting the service type to LoadBalancer enables external access to the ENBUILD UI service. Simply configure the service type as LB to allow external traffic. Refer to the example helm input file for guidance.

Option 2: Use Service Type NodePort#

Configuring the service type as NodePort provides accessibility by exposing a specific port on all nodes in the cluster. Access the ENBUILD UI using the designated node port.

Refer to the example helm input file for guidance.

Option 3: Use Ingress Controller#

Installation and configuration of an Ingress controller within the Kubernetes cluster are prerequisites for this option. Expose the ENBUILD UI service through Ingress configuration for enhanced routing and management of external traffic. Refer to the example helm input file for guidance.

Option 4: Expose Using Istio Virtual Service#

(Istio installation)[(docs/how-to-guides/installing-istio/)] and configuration are required for leveraging this option. Set the istio.enabled parameter to true and provide the necessary configurations, such as the Istio Virtual Service, to expose the ENBUILD UI service. Refer to the example helm input file for guidance.