Upgrade to v0.9.14
3 minute read
This page describes how to upgrade the United Manufacturing Hub to version 0.9.14. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
Add Helm repo in UMHLens / OpenLens
Check if the UMH Helm repository is added in UMHLens / OpenLens.
To do so, from the top-left menu, select FIle > Preferences (or press CTRL + ,
).
Click on the Kubernetes tab and check if the Helm Chart section contains
the https://repo.umh.app
repository.
If it doesn’t, click the Add Custom Helm Repo button and fill in the following values:
- Helm repo name: united-manufacturing-hub
- URL: https://repo.umh.app
Then click Add.
Clear Workloads
Some workloads need to be deleted before upgrading. This process does not delete any data, but it will cause downtime. If a workload is missing, it means that it was not enabled in your cluster, therefore you can skip it.
To delete a resource, you can select it using the box on the left of the resource name and click the - button on the bottom right corner.
- Open the Workloads tab.
- From the Deployment section, delete the following deployments:
- united-manufacturing-hub-factoryinsight-deployment
- united-manufacturing-hub-opcuasimulator-deployment
- united-manufacturing-hub-iotsensorsmqtt
- united-manufacturing-hub-grafanaproxy
- From the StatefulSet section, delete the following statefulsets:
- united-manufacturing-hub-hivemqce
- united-manufacturing-hub-kafka
- united-manufacturing-hub-nodered
- united-manufacturing-hub-sensorconnect
- united-manufacturing-hub-mqttbridge
- Open the Network tab.
- From the Services section, delete the following services:
- united-manufacturing-hub-kafka
Upgrade Helm Chart
Now everything is ready to upgrade the Helm chart.
Navigate to the Helm > Releases tab.
Select the united-manufacturing-hub release and click Upgrade.
In the Helm Upgrade window, make sure that the
Upgrade version
field contains the version you want to upgrade to.You can also change the values of the Helm chart, if needed. For example, if you want to apply the new tweaks to the resources in order to avoid the Out Of Memory crash of the MQTT Broker, you can change the following values:
iotsensorsmqtt: resources: requests: cpu: 10m memory: 20Mi limits: cpu: 30m memory: 50Mi grafanaproxy: resources: requests: cpu: 100m limits: cpu: 300m kafkatopostgresql: resources: requests: memory: 150Mi limits: memory: 300Mi opcuasimulator: resources: requests: cpu: 10m memory: 20Mi limits: cpu: 30m memory: 50Mi packmlmqttsimulator: resources: requests: cpu: 10m memory: 20Mi limits: cpu: 30m memory: 50Mi tulipconnector: resources: limits: cpu: 30m memory: 50Mi requests: cpu: 10m memory: 20Mi redis: master: resources: limits: cpu: 100m memory: 100Mi requests: cpu: 50m memory: 50Mi mqtt_broker: resources: limits: cpu: 700m memory: 1700Mi requests: cpu: 300m memory: 1000Mi
You can also enable the new container registry by changing the values in the
image
orimage.repository
fields from unitedmanufacturinghub/<image-name> to ghcr.io/united-manufacturing-hub/<image-name>.Click Upgrade.
The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.