Breadcrumbs

K8s/Openshift - VeridiumID Server Upgrade Procedure - 3.8.1 to 3.8.4

1. Prerequisites

Please install the following software on the machine that will be used to deploy VeridiumID:

2. Download docker images

The download links for the Docker images are provided in the VeridiumID_3.8.4_images file.

3. Change directory to the folder where values folder is located

4. Download required files

wget --user <NEXUS_USER> --password <NEXUS_PWD> https://veridium-repo.veridium-dev.com/repository/helm-releases/veridiumid-containers/3.8.4/veridiumid-saas-3.8.4.zip
unzip -o veridiumid-saas-3.8.4.zip -d 3.8.4

5. Upgrade VeridiumID

Add the following in veridiumid-values.yaml:

vid-setupagent:

  imagePullSecrets:
    - name: vid-credentials-ecr
  image:
    repository: <DOCKER_REGISTRY_URL>/veridiumid/vid-setupagent
  waitContainer:
    image:
      repository: <DOCKER_REGISTRY_URL>/veridiumid/vid-setupagent
  resources:
    requests:
      cpu: 200m
      memory: 256Mi
    limits:
      cpu: 500m
      memory: 512Mi

Next, execute:

helm upgrade --install -n <NAMESPACE> -f values/veridiumid-values.yaml veridiumid ./3.8.4/helm/veridiumid-0.9.0.tgz --timeout 20m

The NAMESPACE and ENV_NO variables should be set according to your existing installation.

6. Post upgrade configuration

In the vid-maintenance pod, execute the following:

bash /scripts/migrate_to_elk.sh

7. Update API definitions

Apply the latest dmz-api.3.8.4.json and websec-api.3.8.4.json files in the /api folder.

Last updated: