Update process for Kubernetes

This section describes how to update a Kubernetes-based XDM installation.

Always create a database backup and ensure that volume data is safe before updating.

Updating The Helm Repository

To fetch the latest chart versions:

helm repo update

This updates the local Helm repository index for the XDM chart.

You can list available XDM chart versions with:

helm search repo xdm -l

Adjusting Values And Running Helm Upgrade

Choose the XDM release version you want to install (for example 3.26.11).
Open your values.yaml file and update:
- The XDM version under the xdm.version setting (if set in the values.yaml file).
- Any new or changed parameters introduced by the new release (for example under security, database, persistence, ingress, userManagement).
- Deprecated parameters that must be removed or replaced.
  
  Use the release notes and the chart configuration reference for guidance.

Apply the upgrade using Helm:

helm upgrade <NAME> ubs/xdm \
  -f /path/to/values.yaml \
  --version 3.26.11 \
  --namespace <NAMESPACE>

If you omit --version, Helm installs the latest chart version for XDM.

Monitor pods during rollout:
```
kubectl get pods --namespace <NAMESPACE>
kubectl describe pod <core-pod-name> --namespace <NAMESPACE>
kubectl logs <core-pod-name> --namespace <NAMESPACE>
kubectl logs <postgres-pod-name> --namespace <NAMESPACE>
```
Check for:
- Successful startup of all pods.
- Liquibase migration logs in the core and PostgreSQL pods.
- No InvalidClassException or deserialization errors in the core logs (indicating session issues).
- No Liquibase lock errors.

If the core pod remains in Init or CrashLoopBackOff, also verify the persistent volume configuration (for example persistence section and accessMode such as ReadWriteMany for shared volumes).

After the update is complete:

Verify the UI access via the Ingress domain.
Re-run the installation verification, including:
- Logging in to the UI.
- Running a simple smoke test task.
- Executing the persistence restart test as described in Persistence Check (Restart Test).

For typical problems during the update process and their solutions have a look into the Troubleshooting section.