1. Quick start

This section explains how the system (edge and server) can be setup quickly on a single edge device. This is only recommended for development and testing environments.


  • k3os (AMD64) installed on a bootable USB-stick (you can get it here: https://github.com/rancher/k3os/releases/ ). You can create a bootable USB-stick using balenaEtcher
  • a laptop with SSH / SFTP client (e.g. MobaXTerm) and Lens (for accessing the Kubernetes cluster) installed
  • a edge device (currently only x86 systems supported)
  • keyboard, monitor, cables
  • A GitHub account with a public key. If you do not know how to do it check out this tutorial. You can download puttygen here
  • network setup and internet access according to the image below



  1. Install k3OS on your edge device using the bootable USB-stick (Press “entf or delete” repeatedly to enter the BIOS of the Factorycube and then boot from the USB stick with K3OS)
  2. Choose the desired partition (in most cases 1)
  3. Do not use a cloud configuration file
  4. When asked, enter your GitHub username. In the future you will access the device via SSH with your private key. After the installation the system will reboot and show after successfull startup the IP adress of the device. If no IP is shown please check your network setup (especially whether you have DHCP activated).
  5. Configure K3OS as “server”
  6. Remove the USB stick after the message that the system will restart in 5 seconds.
  7. You can now disconnect Monitor and keyboard as you will do everything else via SSH.

General setup

  1. Connect via SSH e.g. with MobaXTerm (Username: rancher, Port: 22, remote host: ip of your edge device)
  2. Authenticate with your private key which belongs to the to the public key stored in Github. (For MobaXTerm: Advanced SSH Settings -> private key and select your private key)
  3. confirm the setting and connect
  4. Install helm on your edge device
export VERIFY_CHECKSUM=false 
curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 
chmod 700 get_helm.sh && ./get_helm.sh
  1. Clone or copy the content of the united-manufacturing-hub repository on Github into the home folder (/home/rancher/united-manufacturing-hub).
  2. Execute cat /etc/rancher/k3s/k3s.yaml to retrieve the secrets to connect to your Kubernetes cluster
  3. Paste the file into Lens when adding a new cluster and adjust the IP (only change the IP address. The port, the numbers after the colon, remain the same). You should now see the cluster in Lens.
  4. Create two namespaces in your Kubernetes cluster called factorycube-edge and factorycube-server by executing the following command:
kubectl create namespace factorycube-edge && kubectl create namespace factorycube-server

Install factorycube-edge

Warning: in production you should use your own certificates and not the ones provided by us as this is highly insecure when exposed to the internet and any insecure network. A tutorial to setup PKI infrastructure for MQTT according to this guide

  1. Go into the folder /home/rancher/united-manufacturing-hub/deployment/factorycube-edge
  2. Create a new file called development_values.yaml using touch development_values.yaml
  3. Copy the following content to that file or use the following example development_values.yaml.
  4. (Only if you did not use example file) Copy the certificates in deplotment/factorycube-server/developmentCertificates/pki/ and then ca.crt, issued/TESTING.crt and issued/private/TESTING.key into development_values.yaml. Additionally use as mqttBridgeURL ssl://factorycube-server-vernemq-local-service.factorycube-server:8883.
  5. Adjust iprange to your network IP range

Example for development_values.yaml:

mqttBridgeURL: "ssl://mqtt.umh.app:8883"
mqttBridgeTopic: "ia/factoryinsight"
  iprange: ""
mqttBridgeCACert: |
mqttBridgeCert: |
mqttBridgePrivkey: |
  1. Execute helm install factorycube-edge /home/rancher/united-manufacturing-hub/deployment/factorycube-edge --values "/home/rancher/united-manufacturing-hub/deployment/factorycube-edge/development_values.yaml" --set serialNumber=$(hostname) --kubeconfig /etc/rancher/k3s/k3s.yaml -n factorycube-edge (change kubeconfig and serialNumber accordingly) (Please pay attention to the correct path. The path may be /home/rancher/united-manufacturing-hub-main … or similar)

Install factorycube-server

Warning: in production this should be installed on a seperate device / in the cloud to ensure High Availability and provide automated backups.

  1. Configure values.yaml according to your needs. For the development version you do not need to do anything. For help in configuring you can take a look into the respective documentation of the subcharts (Grafana, redis, timescaleDB, verneMQ) or into the documentation of the subcomponents (factoryinsight, mqtt-to-postgresql)
  2. Execute helm install factorycube-server /home/rancher/united-manufacturing-hub/deployment/factorycube-server --values "/home/rancher/united-manufacturing-hub/deployment/factorycube-server/values.yaml" --kubeconfig /etc/rancher/k3s/k3s.yaml -n factorycube-server and wait. Helm will automatically install the entire stack across multiple node. It can take up to several minutes until everything is setup. (Please pay attention to the correct path. The path may be /home/rancher/united-manufacturing-hub-main … or similar)

Everything should be now successfully setup and you can connect your edge devices and start creating dashboards! Keep in mind: the default development_values.yaml should only be used for development environments and never for production. See also notes below.

Using it

You can now access Grafana and nodered via HTTP / HTTPS (depending on your setup). Default user for Grafana is admin. You can find the password in the secret RELEASE-NAME-grafana. Grafana is available via port 8080, nodered via 1880.