This is the multi-page printable view of this section. Click here to print.
The United Manufacturing Hub is a continuously evolving product. This means that new features and bug fixes are added to the product on a regular basis. This section contains the upgrading guides for the different versions the United Manufacturing Hub.
The upgrading process is done by upgrading the Helm chart.
This page describes how to upgrade the United Manufacturing Hub to version 0.9.34. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
All the following commands are to be run from the UMH instance’s shell.
Fetch the latest Helm charts from the UMH repository:
sudo $(which helm) repo update --kubeconfig /etc/rancher/k3s/k3s.yaml
Some workloads need to be deleted before upgrading. This process does not delete any data, but it will cause downtime.
sudo $(which kubectl) -n united-manufacturing-hub --kubeconfig /etc/rancher/k3s/k3s.yaml delete deployment united-manufacturing-hub-factoryinsight-deployment united-manufacturing-hub-iotsensorsmqtt united-manufacturing-hub-opcuasimulator-deployment
sudo $(which kubectl) -n united-manufacturing-hub --kubeconfig /etc/rancher/k3s/k3s.yaml delete statefulset united-manufacturing-hub-hivemqce united-manufacturing-hub-kafka united-manufacturing-hub-nodered united-manufacturing-hub-sensorconnect united-manufacturing-hub-mqttbridge
Upgrade the Helm chart to the 0.9.34 version:
sudo helm upgrade united-manufacturing-hub united-manufacturing-hub/united-manufacturing-hub -n united-manufacturing-hub --version 0.9.34 --reuse-values --kubeconfig /etc/rancher/k3s/k3s.yaml \
--set kafkatopostgresqlv2.enabled=false \
--set kafkatopostgresqlv2.image.repository=ghcr.io/united-manufacturing-hub/kafka-to-postgresql-v2 \
--set kafkatopostgresqlv2.image.pullPolicy=IfNotPresent \
--set kafkatopostgresqlv2.replicas=1 \
--set kafkatopostgresqlv2.resources.limits.cpu=1000m \
--set kafkatopostgresqlv2.resources.limits.memory=300Mi \
--set kafkatopostgresqlv2.resources.requests.cpu=100m \
--set kafkatopostgresqlv2.resources.requests.memory=150Mi \
--set kafkatopostgresqlv2.probes.startup.failureThreshold=30 \
--set kafkatopostgresqlv2.probes.startup.initialDelaySeconds=10 \
--set kafkatopostgresqlv2.probes.startup.periodSeconds=10 \
--set kafkatopostgresqlv2.probes.liveness.periodSeconds=5 \
--set kafkatopostgresqlv2.probes.readiness.periodSeconds=5 \
--set kafkatopostgresqlv2.logging.level=PRODUCTION \
--set kafkatopostgresqlv2.asset.cache.lru.size=1000 \
--set kafkatopostgresqlv2.workers.channel.size=10000 \
--set kafkatopostgresqlv2.workers.goroutines.multiplier=16 \
--set kafkatopostgresqlv2.database.user=kafkatopostgresqlv2 \
--set kafkatopostgresqlv2.database.password=changemetoo \
--set _000_commonConfig.datamodel_v2.enabled=true \
--set _000_commonConfig.datamodel_v2.bridges[0].mode=mqtt-kafka \
--set _000_commonConfig.datamodel_v2.bridges[0].brokerA=united-manufacturing-hub-mqtt:1883 \
--set _000_commonConfig.datamodel_v2.bridges[0].brokerB=united-manufacturing-hub-kafka:9092 \
--set _000_commonConfig.datamodel_v2.bridges[0].topic=umh.v1..* \
--set _000_commonConfig.datamodel_v2.bridges[0].topicMergePoint=5 \
--set _000_commonConfig.datamodel_v2.bridges[0].partitions=6 \
--set _000_commonConfig.datamodel_v2.bridges[0].replicationFactor=1 \
--set _000_commonConfig.datamodel_v2.database.name=umh_v2 \
--set _000_commonConfig.datamodel_v2.database.host=united-manufacturing-hub \
--set _000_commonConfig.datamodel_v2.grafana.dbreader=grafanareader \
--set _000_commonConfig.datamodel_v2.grafana.dbpassword=changeme
There has been some changes to the database, which need to be applied. This process does not delete any data.
sudo $(which kubectl) -n united-manufacturing-hub --kubeconfig /etc/rancher/k3s/k3s.yaml exec -it united-manufacturing-hub-timescaledb-0 -c timescaledb -- sh -c ". /etc/timescaledb/post_init.d/0_create_dbs.sh; . /etc/timescaledb/post_init.d/1_set_passwords.sh"
sudo $(which kubectl) rollout restart deployment united-manufacturing-hub-kafkatopostgresqlv2 -n united-manufacturing-hub --kubeconfig /etc/rancher/k3s/k3s.yaml
This page describes how to upgrade the United Manufacturing Hub to version 0.9.15. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
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.
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. If you want to activate the new databridge you need to add & edit the following section
_000_commonConfig:
...
datamodel_v2:
enabled: true
bridges:
- mode: mqtt-kafka
brokerA: united-manufacturing-hub-mqtt:1883 # The flow is always from A->B, for omni-directional flow, setup a 2nd bridge with reversed broker setup
brokerB: united-manufacturing-hub-kafka:9092
topic: umh.v1..* # accept mqtt or kafka topic format. after the topic seprator, you can use # for mqtt wildcard, or .* for kafka wildcard
topicMergePoint: 5 # This is a new feature of our datamodel_old, which splits topics in topic and key (only in Kafka), preventing having lots of topics
partitions: 6 # optional: number of partitions for the new kafka topic. default: 6
replicationFactor: 1 # optional: replication factor for the new kafka topic. default: 1
...
You can also enable the new container registry by changing the values in the
image or image.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.
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.
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:
Then click Add.
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.
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 or image.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.
This page describes how to upgrade the United Manufacturing Hub to version 0.9.13. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
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.
Now everything is ready to upgrade the Helm chart.
Upgrade version field
contains the version you want to upgrade to.The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.
This page describes how to upgrade the United Manufacturing Hub to version 0.9.12. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
This step is only needed if you enabled RBAC for the MQTT Broker and changed the default password. If you did not change the default password, you can skip this step.
credentials.xml and save it in a safe place.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.
In this version we reduced the size of the MQTT Broker extension PVC. To do so, we need to delete the old PVC and create a new one. This process will set the credentials of the MQTT Broker to the default ones. If you changed the default password, you can restore them after the upgrade.
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.
There are some incompatible changes in this version. To avoid errors, you need to change the following values:
Remove property console.console.config.kafka.tls.passphrase:
console:
console:
config:
kafka:
tls:
passphrase: "" # <- remove this line
console.extraContainers: remove the property and its content.
console:
extraContainers: {} # <- remove this line
console.extraEnv: remove the property and its content.
console:
extraEnv: "" # <- remove this line
console.extraEnvFrom: remove the property and its content.
console:
extraEnvFrom: "" # <- remove this line
console.extraVolumeMounts: remove the |- characters right after the
property name. It should look like this:
console:
extraVolumeMounts: # <- remove the `|-` characters in this line
- name: united-manufacturing-hub-kowl-certificates
mountPath: /SSL_certs/kafka
readOnly: true
console.extraVolumes: remove the |- characters right after the
property name. It should look like this:
console:
extraVolumes: # <- remove the `|-` characters in this line
- name: united-manufacturing-hub-kowl-certificates
secret:
secretName: united-manufacturing-hub-kowl-secrets
Change the console.service property to the following:
console:
service:
type: LoadBalancer
port: 8090
targetPort: 8080
Change the Redis URI in factoryinsight.redis:
factoryinsight:
redis:
URI: united-manufacturing-hub-redis-headless:6379
Set the following values in the kafka section to true, or add them if
they are missing:
kafka:
externalAccess:
autoDiscovery:
enabled: true
enabled: true
rbac:
create: true
Change redis.architecture to standalone:
redis:
architecture: standalone
redis.sentinel: remove the property and its content.
redis:
sentinel: {} # <- remove all the content of this section
Remove the property redis.master.command:
redis:
master:
command: /run.sh # <- remove this line
timescaledb-single.fullWalPrevention: remove the property and its content.
timescaledb-single:
fullWalPrevention: # <- remove this line
checkFrequency: 30 # <- remove this line
enabled: false # <- remove this line
thresholds: # <- remove this line
readOnlyFreeMB: 64 # <- remove this line
readOnlyFreePercent: 5 # <- remove this line
readWriteFreeMB: 128 # <- remove this line
readWriteFreePercent: 8 # <- remove this line
timescaledb-single.loadBalancer: remove the property and its content.
timescaledb-single:
loadBalancer: # <- remove this line
annotations: # <- remove this line
service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: "4000" # <- remove this line
enabled: true # <- remove this line
port: 5432 # <- remove this line
timescaledb-single.replicaLoadBalancer: remove the property and its content.
timescaledb-single:
replicaLoadBalancer:
annotations: # <- remove this line
service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: "4000" # <- remove this line
enabled: false # <- remove this line
port: 5432 # <- remove this line
timescaledb-single.secretNames: remove the property and its content.
timescaledb-single:
secretNames: {} # <- remove this line
timescaledb-single.unsafe: remove the property and its content.
timescaledb-single:
unsafe: false # <- remove this line
Change the value of the timescaledb-single.service.primary.type property
to LoadBalancer:
timescaledb-single:
service:
primary:
type: LoadBalancer
Click Upgrade.
The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.
This page describes how to upgrade the United Manufacturing Hub to version 0.9.11. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
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.
Now everything is ready to upgrade the Helm chart.
Upgrade version field
contains the version you want to upgrade to.The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.
This page describes how to upgrade the United Manufacturing Hub to version 0.9.10. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
In this release, the Grafana version has been updated from 8.5.9 to 9.3.1. Check the release notes for further information about the changes.
Additionally, the way default plugins are installed has changed. Unfortunatly, it is necesary to manually install all the plugins that were previously installed.
If you didn’t install any plugin other than the default ones, you can skip this section.
Follow these steps to see the list of plugins installed in your cluster:
Open the browser and go to the Grafana dashboard.
Navigate to the Configuration > Plugins tab.
Select the Installed filter.
Write down all the plugins that you manually installed. You can recognize
them by not having the Core tag.
The following ones are installed by default, therefore you can skip them:
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.
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.
In the grafana section, find the extraInitContainers field and change
its value to the following:
- image: unitedmanufacturinghub/grafana-umh:1.1.2
name: init-plugins
imagePullPolicy: IfNotPresent
command: ['sh', '-c', 'cp -r /plugins /var/lib/grafana/']
volumeMounts:
- name: storage
mountPath: /var/lib/grafana
Make these changes in the kafka section:
Set the value of the heapOpts field to -Xmx2048m -Xms2048m.
Replace the content of the resources section with the following:
limits:
cpu: 1000m
memory: 4Gi
requests:
cpu: 100m
memory: 2560Mi
Click Upgrade.
The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.
Afterwards, you can reinstall the additional Grafana plugins.
In this upgrade we switched from using VerneMQ to HiveMQ as our MQTT Broker (you can read the blog article about it).
While this process is fully backwards compatible, we suggest to update NodeRed flows and any other additional service that uses MQTT, to use the new service broker called united-manufacturing-hub-mqtt. The old united-manufacturing-hub-vernemq is still functional and, despite the name, also points to HiveMQ, but in future upgrades will be removed.
Additionally, for production environments, we recommend to enable RBAC for the MQTT Broker.
Please double-check if all of your services can connect to the new MQTT broker. It might be needed for them to be restarted, so that they can resolve the DNS name and get the new IP. Also, it can happen with tools like chirpstack, that you need to specify the client-id as the automatically generated ID worked with VerneMQ, but is now declined by HiveMQ.
If you are using the united-manufacturing-hub-mqtt service, but some microservice can’t connect to it, restarting the microservice might solve the issue. To do so, you can delete the Pod of the microservice and let Kubernetes recreate it.
ChirpStack uses a generated client-id to connect to the MQTT broker. This
client-id is not accepted by HiveMQ. To solve this issue, you can set the
client_id field in the integration.mqtt section of the chirpstack configuration
file to a fixed value:
[integration]
...
[integration.mqtt]
client_id="chirpstack"
This page describes how to upgrade the United Manufacturing Hub to version 0.9.9. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
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.
Now everything is ready to upgrade the Helm chart.
Upgrade version field
contains the version you want to upgrade to.grafana section, find the extraInitContainers field and change the
value of the image field to unitedmanufacturinghub/grafana-plugin-extractor:0.1.4.The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.
This page describes how to upgrade the United Manufacturing Hub to version 0.9.8. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
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.
Now everything is ready to upgrade the Helm chart.
Upgrade version field
contains the version you want to upgrade to.The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.
This page describes how to upgrade the United Manufacturing Hub to version 0.9.7. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
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.
Now everything is ready to upgrade the Helm chart.
Upgrade version field
contains the version you want to upgrade to.Make these changes in the grafana section:
Replace the content of datasources with the following:
datasources.yaml:
apiVersion: 1
datasources:
- access: proxy
editable: false
isDefault: true
jsonData:
apiKey: $FACTORYINSIGHT_PASSWORD
apiKeyConfigured: true
customerId: $FACTORYINSIGHT_CUSTOMERID
serverURL: http://united-manufacturing-hub-factoryinsight-service/
name: umh-datasource
orgId: 1
type: umh-datasource
url: http://united-manufacturing-hub-factoryinsight-service/
version: 1
- access: proxy
editable: false
isDefault: false
jsonData:
apiKey: $FACTORYINSIGHT_PASSWORD
apiKeyConfigured: true
baseURL: http://united-manufacturing-hub-factoryinsight-service/
customerID: $FACTORYINSIGHT_CUSTOMERID
name: umh-v2-datasource
orgId: 1
type: umh-v2-datasource
url: http://united-manufacturing-hub-factoryinsight-service/
version: 1
Replace the content of env with the following:
GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS: umh-datasource,umh-factoryinput-panel,umh-v2-datasource
Replace the content of extraInitContainers with the following:
- name: init-umh-datasource
image: unitedmanufacturinghub/grafana-plugin-extractor:0.1.3
volumeMounts:
- name: storage
mountPath: /var/lib/grafana
imagePullPolicy: IfNotPresent
In the timescaledb-single section, make sure that the image.tag field
is set to pg13.8-ts2.8.0-p1.
The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.
The Factoryinsight API version has changed from v1 to v2. To make sure that
you are using the new version, click on any Factoryinsight Pod and check that the
VERSION environment variable is set to 2.
If it’s not, follow these steps:
Click the Edit button to open the deployment’s configuration.
spec.template.spec.containers[0].env field.value field of the VERSION variable to 2.This page describes how to upgrade the United Manufacturing Hub to version 0.9.6. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
In this version, a new index has been added to the processValueTabe table,
allowing to speed up the queries.
sudo $(which kubectl) exec -it $(sudo $(which kubectl) get pods --kubeconfig /etc/rancher/k3s/k3s.yaml -n united-manufacturing-hub -l app.kubernetes.io/component=timescaledb -o jsonpath="{.items[0].metadata.name}") --kubeconfig /etc/rancher/k3s/k3s.yaml -n united-manufacturing-hub -- psql -U postgres
This command will open a psql shell connected to the default postgres database.
Execute the following query:
CREATE INDEX ON processvaluetable(valuename, asset_id) WITH (timescaledb.transaction_per_chunk);
REINDEX TABLE processvaluetable;
This command could take a while to complete, especially on larger tables.
Type exit to close the shell.
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.
Now everything is ready to upgrade the Helm chart.
Upgrade version field
contains the version you want to upgrade to.The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.
This page describes how to upgrade the United Manufacturing Hub to version 0.9.5. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
In this version, one of the constraints of the ordertable table has been
modified.
Make sure to backup the database before exectuing the following steps.
sudo $(which kubectl) exec -it $(sudo $(which kubectl) get pods --kubeconfig /etc/rancher/k3s/k3s.yaml -n united-manufacturing-hub -l app.kubernetes.io/component=timescaledb -o jsonpath="{.items[0].metadata.name}") --kubeconfig /etc/rancher/k3s/k3s.yaml -n united-manufacturing-hub -- psql -U postgres
This command will open a psql shell connected to the default postgres database.
Check for possible conflicts in the ordertable table:
SELECT order_name, asset_id, count(*) FROM ordertable GROUP BY order_name, asset_id HAVING count(*) > 1;
If the result is empty, you can skip the next step.
Delete the duplicates:
DELETE FROM ordertable ox USING (
SELECT MIN(CTID) as ctid, order_name, asset_id
FROM ordertable
GROUP BY order_name, asset_id HAVING count(*) > 1
) b
WHERE ox.order_name = b.order_name AND ox.asset_id = b.asset_id
AND ox.CTID <> b.ctid;
If the data cannot be deleted, you have to manually update each duplicate
order_names to a unique value.
Get the name of the constraint:
SELECT conname FROM pg_constraint WHERE conrelid = 'ordertable'::regclass AND contype = 'u';
Drop the constraint:
ALTER TABLE ordertable DROP CONSTRAINT ordertable_asset_id_order_id_key;
Add the new constraint:
ALTER TABLE ordertable ADD CONSTRAINT ordertable_asset_id_order_name_key UNIQUE (asset_id, order_name);
Now you can close the shell by typing exit and continue with the upgrade process.
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.
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.
Enable the startup probe for the Kafka Broker by adding the following into
the kafka section:
startupProbe:
enabled: true
failureThreshold: 600
periodSeconds: 10
timeoutSeconds: 10
Click Upgrade.
The upgrade process can take a few minutes. The upgrade is complete when the Status field of the release is Deployed.
Some messages have been modified in this version. You need to update some payolads in your Node-RED flows.
start_time_stamp has been renamed to timestamp_msend_time_stamp has been renamed to timestamp_ms_endstart_time_stamp has been renamed to timestamp_msend_time_stamp has been renamed to timestamp_ms_enddeleteShiftByAssetIdAndBeginTimestamp and deleteShiftById have been removed.
Use the deleteShift
message instead.This page describes how to upgrade the United Manufacturing Hub to version 0.9.4. Before upgrading, remember to backup the database, Node-RED flows, and your cluster configuration.
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:
Then click Add.
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.
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.
If you have enabled the Kafka Bridge,
find the section
_000_commonConfig.kafkaBridge.topicmap and set the value to the following:
- bidirectional: false
name: HighIntegrity
send_direction: to_remote
topic: ^ia\.(([^r.](\d|-|\w)*)|(r[b-z](\d|-|\w)*)|(ra[^w]))\.(\d|-|\w|_)+\.(\d|-|\w|_)+\.((addMaintenanceActivity)|(addOrder)|(addParentToChild)|(addProduct)|(addShift)|(count)|(deleteShiftByAssetIdAndBeginTimestamp)|(deleteShiftById)|(endOrder)|(modifyProducedPieces)|(modifyState)|(productTag)|(productTagString)|(recommendation)|(scrapCount)|(startOrder)|(state)|(uniqueProduct)|(scrapUniqueProduct))$
- bidirectional: false
name: HighThroughput
send_direction: to_remote
topic: ^ia\.(([^r.](\d|-|\w)*)|(r[b-z](\d|-|\w)*)|(ra[^w]))\.(\d|-|\w|_)+\.(\d|-|\w|_)+\.(process[V|v]alue).*$
For more information, see the Kafka Bridge configuration
If you have enabled Barcodereader,
find the barcodereader section and set the
following values, adding the missing ones and updating the already existing
ones:
enabled: false
image:
pullPolicy: IfNotPresent
resources:
requests:
cpu: "2m"
memory: "30Mi"
limits:
cpu: "10m"
memory: "60Mi"
scanOnly: false # Debug mode, will not send data to kafka
Click Upgrade.
The upgrade process can take a few minutes. The process is complete when the Status field of the release is Deployed.