Upgrade VeridiumID Containers from 3.7.2 to v3.8.1
1. Prerequisites
Please install the following software on the machine that will be used to deploy VeridiumID:
Helm 3. Please check your installed version by running
helm version
2. Download docker images
If using a custom Docker registry, please download and unpack the following archive, then upload its contents to your Docker registry.
Name | URL | SHA256 | MD5 |
|---|---|---|---|
veridiumid-saas-images-3.8.1.tar.gz | 4182c4c7f5d02b688504159fcf028a49776980152af7c4502014c22fa5f3ff26 | a29f3611481e550139a56175a35c8cbb |
3. Change directory to the folder where veridium-containers folder is located
4. Download required files
wget --user <NEXUS_USER> --password <NEXUS_PASSWORD> https://veridium-repo.veridium-dev.com/repository/helm-releases/veridiumid-containers/3.8.1/veridiumid-saas-3.8.1.zip
unzip -o veridiumid-saas-3.8.1.zip -d 3.8.1
5. Upgrade Elasticsearch and Kibana.
The NAMESPACE and ENV_NO variables should be set according to your existing installation.
Perform the following modifications:
In
veridiumid-containers/elasticsearch-values.yaml, update the tags of elasticsearch and kibana images to 8.17.2.
# update elasticsearch & kibana
helm upgrade --install -n <NAMESPACE> -f veridiumid-containers/elasticsearch-values.yaml elasticsearch-<ENV_NO> ../3.8.1/helm/elasticsearch-0.3.1.tgz
# force restart, if necessary:
oc -n <NAMESPACE> delete sts elasticsearch-<ENV_NO>-es-default --cascade=orphan
6. Upgrade VeridiumID
The NAMESPACE and ENV_NO variables should be set according to your existing installation.
Remove all occurrences of tag: 11.2.71 in veridiumid-containers/veridiumid-values.yaml
helm upgrade --install -n <NAMESPACE> -f veridiumid-containers/veridiumid-values.yaml veridiumid ../3.8.1/helm/veridiumid-0.7.7.tgz --timeout 20m
7. Post upgrade configuration
In the vid-maintenance pod, execute the following:
bash /scripts/migrate_to_elk.sh
8. Update API definitions
Apply the latest dmz-api.3.8.1.json and websec-api.3.8.1.json files in the /api folder.