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
cat /etc/rancher/k3s/k3s.yamlto retrieve the secrets to connect to your Kubernetes cluster
factorycube-serverby executing the following command:
kubectl create namespace factorycube-edge && kubectl create namespace factorycube-server
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
development_values.yaml. Additionally use as
iprangeto your network IP range
mqttBridgeURL: "ssl://mqtt.umh.app:8883" mqttBridgeTopic: "ia/factoryinsight" sensorconnect: iprange: "172.16.1.0/24" mqttBridgeCACert: | ENTER CERT HERE mqttBridgeCert: | ENTER CERT HERE mqttBridgePrivkey: | ENTER CERT HERE
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)
Warning: in production this should be installed on a seperate device / in the cloud to ensure High Availability and provide automated backups.
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-serverand 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.
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.