This chapter outlines the configuration changes introduced in version 1.5 and provides step-by-step guide instructions for upgrading from version 1.4.

HELM Deployment

Step by Step Upgrade Instructions

1.Deploy the 1.5 Solution Package

Use the Solution Manager to deploy the Solution Package for version 1.5.

Don't forget to set the sharing level of the portal items (see Deploy Network Locator Web App)

2.Update values.yaml.

Update the appUrl parameters for Cockpit and Landing Page using the values provided by the new solution deployment.

3.Uninstall the Existing HELM Deployment

Run the following command to uninstall the current deployment:

helm uninstall <RELEASENAME> --namespace <NAMESPACE>

No data loss will occur during uninstallation. The Locator uses persistent volumes to store essential data, which will remain intact and be reused by the new version.

4.Install the New Version

Deploy version 1.5 using HELM:

helm install <RELEASENAME> oci://vertigisapps.azurecr.io/network-locator/helm-chart \
   --namespace <NAMESPACE> \
   -f values.yaml \
   --wait \
    --version 1.5.0 \
    --timeout 15m0s \

Configuration Changes

The following changes are optional. The upgrade will work even if these features are not configured immediately.

Prohibited Areas

You can now configure layers of type PROHIBITED_AREA to define zones where locate requests are not permitted.

Example configuration:

"Prohibited-Area": {
  "layer-url": "https://<HOST>/server/rest/services/Hosted/Locator_Service_Area/FeatureServer/0",
  "buffer-size": "0.1",
  "type": "PROHIBITED_AREA",
  "show-in-map": true
}

•To visualize these layers in the map, set show-in-map to true.

•If the layer is secured, use the new portal-proxy-url property to route requests through a proxy that injects an API key.

•The API key must be created with the required permissions. Refer to Esri’s documentation here: Create an API Key – Esri Developer Guide

The API-Key needs to be passed in the HELM values in the new parameter apiKey

Kubernetes Ressource Limits

The Locator HELM charts now include default CPU and memory requests and limits for all services.

You can override these defaults in your values.yaml to better match your expected load.

Example for the network-locator-config service:

network-locator-config:
 resources:
   limits:
     cpu: "1000m"
     memory: "1281Mi"
   requests:
     cpu: "500m"
     memory: "32Mi"

These settings follow Kubernetes best practices and help ensure stable resource allocation and scaling behavior.

For a complete list of defaults, refer to the Kubernetes Requirements section.