This chapter outlines the configuration changes introduced in version 1.10 and provides step-by-step guide instructions for upgrading from version 1.9.
In earlier versions, Process Manager ran as a StatefulSet and used a dedicated persistent volume. Starting with this release, Process Manager runs as a Deployment and no longer requires that dedicated PV. Helm upgrade should automatically take care of this. Make sure to verify after the deployment whether the process manager now runs as a deployment and that no StatefulSet exists anymore.
The Helm chart now supports configuring a specific Gateway listener when multiple listeners are present. You can optionally define either the sectionName or the port of the desired listener to ensure traffic is routed through the correct entry point.
This is particularly useful in environments where a Gateway exposes multiple listeners (e.g., for different protocols, domains, or ports), giving you more precise control over how your application is exposed. Both parameters are optional and only need to be added to your values file if the default listener selection does not meet your requirements.
gateway:
name: <GATEWAY-NAME>
namespace: <GATEWAY-NAMESPACE>
# If your gateway has multiple listeners and you want to use a specific one, set the sectionName or port accordingly.
#sectionName: <GATEWAY-LISTENER-NAME>
#port: <GATEWAY-LISTENER-PORT>
1.Back up your Process Manager, Storage, and Sync Service settings by saving the JSON config from the Admin Client to a local file—just in case.
2.Make sure you have a valid connection to your kubernetes cluster
3.Login to the VertiGIS Container Registry
a.helm registry login vertigisapps.azurecr.io
4.Deploy version 1.10 using HELM.
helm upgrade <RELEASENAME> oci://vertigisapps.azurecr.io/network-locator/helm-chart \
--namespace <NAMESPACE> \
-f values.yaml \
--wait \
--version 1.10.0 \
--timeout 30m0s \
This release updates the UI workflow. If you have made custom modifications, make sure to merge them with the updated version.