Documentation Hub
On-Premise
Why Keyless?Start HereMobile SDKWeb SDKWorkforceIDV BridgeUser GuideAdmin portalOn-Premise
On-Premise
Why Keyless?Start HereMobile SDKWeb SDKWorkforceIDV BridgeUser GuideAdmin portalOn-Premise
  • On-Premise Installation Manual
  • Keyless Backend Installation
    • Planning for installation
    • Components
  • Infrastructural requirements
  • Monitoring
  • Installation procedure
    • General Configuration
    • Namespace
    • Helm setup
    • Circuit Storage
    • Node Persistence
    • Metrics Collector
    • Operations Service
    • Core Daemon
    • Administrator Dashboard
  • Upgrade procedure
    • Cluster and Runtime
      • Breaking changes
        • Release 1.3.0
    • Databases
  • Checking the installation completed successfully
  • Helm and Components Versions
Powered by GitBook
On this page

Was this helpful?

  1. Upgrade procedure

Cluster and Runtime

Helm charts are updated from time to time. Customers will be notified of each upgrade.

Customers will need to upgrade the system by using a command similar to:

helm upgrade --install node-persistence keyless/node-persistence --version 0.3.8 --timeout 10m --wait --set image.tag=1.32.2  --atomic -f values.yaml -f secrets.yaml

Applications are also updated from time to time. For each update customers will be notified of a specific tag which has to be set in the overrides of the correct values.yml file. After this the helm chart needs to be upgraded. This will lead to pods being recreated with the new code.

Running an unsupported component version combination may lead to a non functional installation and/or data loss.

Last updated 6 days ago

Was this helpful?