Access Services Outside the Cluster
Some of the microservices in the United Manufacturing Hub are exposed outside the cluster with a LoadBalancer service. A LoadBalancer is a service that exposes a set of Pods on the same network as the cluster, but not necessarily to the entire internet. The LoadBalancer service provides a single IP address that can be used to access the Pods.
Before you begin
You need to have a UMH cluster. If you do not already have a cluster, you can create one by using the Management Console.
Accessing the services
The LoadBalancer service provides a single IP address that can be used to access the Pods. To find the IP address, open UMHLens / OpenLens and navigate to Network > Services. The IP address is listed in the External IP column.
To access the services, use the IP address and the port number of the service,
If you installed the United Manufacturing Hub on your local machine, either
using the Management Console or the command line, the services are accessible
Services with LoadBalancer by default
The following services are exposed outside the cluster with a LoadBalancer service by default:
- Database at port 5432
- Kafka Console at port 8090
- Kafka Broker at port 9094
- Grafana at port 8080
- MQTT Broker at port 1883
- Node-RED at port 1880
- OPCUA Simulator at port 46010
To access Node-RED, you need to use the
/node-red path, e.g.
Services without a LoadBalancer
Some of the microservices in the United Manufacturing Hub are exposed via a ClusterIP service. That means that they are only accessible from within the cluster itself. To access them from outside the cluster, you need to create a LoadBalancer service.
Create a LoadBalancer service
If you are looking to expose th Kafka broker, follow the instructions in the Access Kafka outside the cluster page.
For any other microservice, follow these steps to enable the LoadBalancer service:
Open UMHLens / OpenLens and navigate to Network > Services.
Select the service and click the Edit button.
Scroll down to the
status.loadBalancersection and change it to the following:
status: loadBalancer: ingress: - ip: <external-ip>
<external-ip>with the external IP address of the node.
Scroll to the
spec.typesection and change the value from ClusterIP to LoadBalancer.
Click Save to apply the changes.
If you installed the United Manufacturing Hub on your local machine, either using the Management Console or the command line, you also need to map the port exposed by the k3d cluster to a port on your local machine. To do that, run the following command:
k3d cluster edit united-manufacturing-hub --port-add "<local-port>:<cluster-port>@server:0"
<local-port> with a free port number on your local machine, and
<cluster-port> with the port number of the service.
Port forwarding in UMHLens / OpenLens
If you don’t want to create a LoadBalancer service, effectively exposing the microservice to anyone that has access to the host IP address, you can use UMHLens / OpenLens to forward the port to your local machine.
- Open UMHLens / OpenLens and navigate to Network > Services.
- Select the service that you want to access.
- Scroll down to the Connection section and click the Forward… button.
- From the dialog, you can choose a port on your local machine to forward the cluster port from, or you can leave it empty to use a random port.
- Click Forward to apply the changes.
- If you left the checkbox Open in browser checked, then the service will open in your default browser.
You can see and manage the forwarded ports of your cluster in the Network > Port Forwarding section.
There are some security considerations to keep in mind when exposing the MQTT broker.
By default, the MQTT broker is configured to allow anonymous connections. This means that anyone can connect to the broker without providing any credentials. This is not recommended for production environments.
If you are using a version of the United Manufacturing Hub older than 0.9.10, then you need to change the ACL configuration to allow your MQTT client to connect to the broker.
LoadBalancer service stuck in Pending state
If the LoadBalancer service is stuck in the Pending state, it probably means
that the host port is already in use. To fix this, edit the service and change
spec.ports.port to a different port number.