Migration guide for Redis Sentinel

Updated in 4.53

Live Agent has been put in maintenance mode. The product will continue to be maintained in the foreseeable future. Users can continue to fully rely on Live Agent being available. In future releases, only security updates and bug fixes will be provided; no new features will be released.

This migration guide is for the Live Agent 4.53 version upgrade. This release upgrades the Redis chart to use Redis Sentinel for high availability.

Perform Standard Upgrades

The first step is to perform a standard upgrade of the Live Agent chart to the desired new version to ensure the migration job is run before enabling Redis Sentinel. If the values were not specified previously, ensure that Sentinel mode is disabled in the values.yaml file.

redis:
  enabled: true
  sentinel:
    enabled: false
# ...

Upgrade the chart to the latest version.

 helm upgrade cognigy-live-agent oci://cognigy.azurecr.io/helm/live-agent --version X.X.X --namespace live-agent -f custom-values.yaml

Change values.yaml

The new values for version 4.53 already include the new Redis Sentinel configuration. If you use a custom values.yaml file, ensure it does not override the new Redis Sentinel configuration.

# ...

redis:
  enabled: true
  sentinel:
    enabled: true
# ...

Change the Migration Job Hooks

The migration job hooks must be temporarily changed to post-install,post-upgrade to run the migration job after the upgrade. Otherwise, the migration job will run before new Redis pods are created, resulting in a failed migration.

# migration job (uncomment if needed)
migration:
  enabled: true
  hooks:
    migrate:
      # the setting here will override the default, which is "post-install,pre-upgrade"
      hookAnnotation: "post-install,post-upgrade"

Upgrade the chart

Upgrade the chart to the latest version.

 helm upgrade cognigy-live-agent oci://cognigy.azurecr.io/helm/live-agent --version X.X.X --namespace live-agent -f custom-values.yaml

Verify Functionality and Pod Status

Ensure that the pods are running and the application is functioning correctly, including passing the startup health check.

kubectl get pods

Remove the Old PVCs and PVs

Remove the previous PVCs used by the Redis pods before the upgrade. They are typically named as follows:

redis-data-cognigy-live-agent-redis-master-0
redis-data-cognigy-live-agent-redis-replicas-0

To remove the previous PVCs and PVS, follow these steps:

Check that PVCs’ status is now Released:
kubectl get pvc -n live-agent

Delete PVCs.

kubectl delete pvc redis-data-cognigy-live-agent-redis-master-0 -n live-agent
kubectl delete pvc redis-data-cognigy-live-agent-redis-replicas-0 -n live-agent

Check that the PVs are now Available.
kubectl get pv

Delete PVs.

kubectl delete pv <pv_name> # replace <pv_name> with the name of the PV associated with the deleted PVCs

Remove the Migration Job Hooks after the Upgrade

Remove the migration job hooks from the values.yaml file that was added in the previous step and revert to the default value after the upgrade.

# migration job (uncomment if needed)
# migration:
#   enabled: true
#   hooks:
#     migrate:
#       hookAnnotation: "post-install,pre-upgrade"

If you have any issues, contact technical support.

Overview

Conversations

Assistants

Analytics Tools

Configure

Access Management

User Profile and Notifications

Miscellaneous

Perform Standard Upgrades

Change values.yaml

Change the Migration Job Hooks

Upgrade the chart

Verify Functionality and Pod Status

Remove the Old PVCs and PVs

Remove the Migration Job Hooks after the Upgrade

​Perform Standard Upgrades

​Change values.yaml

​Change the Migration Job Hooks

​Upgrade the chart

​Verify Functionality and Pod Status

​Remove the Old PVCs and PVs

​Remove the Migration Job Hooks after the Upgrade

Perform Standard Upgrades

Change values.yaml

Change the Migration Job Hooks

Upgrade the chart

Verify Functionality and Pod Status

Remove the Old PVCs and PVs

Remove the Migration Job Hooks after the Upgrade