Skip to main content
LILT relies on third-party apps for operation, a majority of which can be upgraded with no concerns. As of LILT version 5.1, the following third-party apps are utilized:
  • Clickhouse
  • Elasticsearch
  • Flannel
  • Grafana
  • Ingress-nginx
  • Istio
  • Localpv-provisioner
  • Minio
  • Mongodb
  • Rabbitmq
  • MySql
  • Prometheus
  • Redis
All apps are designed to upgrade in place with PVC (persistent storage) remaining bound to the new pods. The two apps of most concern are MySql and Minio, which retain all LILT data. The other third-party apps do have persistent data in cache but will be automatically rewritten if an upgrade fails.

Upgrade

Upgrade apps by running the following respective helm script (using Clickhouse as an example):
This runs a helm upgrade command that adds a new version of the app, allowing for helm rollback if necessary. Be cautious of using helm delete as this removes all previous versions and deletes all persistent data for the app..

Backup App Data

As a precaution, data can be backed up for MySql and Minio in case of data loss during upgrades

1. Disable Front

As best practice, disable LILT frontaccess so that no data is written to MySql or Minio during backup/restore. Disable front:

2. Backup/Restore MySql

Exec to MySql pod and create a db dump file. That file can then be backed up on another local machine:
To restore the backup, copy the dump file from local machine to the upgraded MtSql pod and restore:

3. Backup/Restore Minio

Minio uses basic object storage that is persisted with a PVC. The PVC data can simply be backed up and then copied to a new PVC:
All relevant data is stored in a subdirectory of the pvc lilt. To restore, copy the old lilt directory to the new pvc. NOTE: do NOT overwrite existing data in the new PVC:

4. Enable Front

Reenable LILT front: