Skip to content

Upgrading Helm Deployment

This section describes how to update the configuration of an HCL Digital Experience (DX) 9.5 CF196 or later deployment to Kubernetes or OpenShift installed using Helm.

This section assumes that you prepared your cluster and your custom-values.yaml file, using guidance provided in the Preparation before installing HCL DX using Helm topic, and then installed your deployment using the instructions in the Install topic.

Overview of Helm Configuration Updates

After an HCL DX Kubernetes 9.5 deployment is installed, all configuration changes are made by updating the custom-values.yaml file used to install the deployment. This way, your custom-values.yaml file remains an up-to-date description of the configuration of your environment.

Prerequisites

Make sure that the wkplc_dbdomain.properties file is correct. The HCL DX upgrade runs several ConfigEngine scripts. These scripts depend on the wkplc_dbdomain.properties being up-to-date and accurate, especially with the password properties.

Edit the (wp_profile root)/ConfigEngine/properties/wkplc_dbdomain.properties file and ensure the following values are set correctly:

  • release.DbPassword=(your database user password)
  • community.DbPassword=(your database user password)
  • customization.DbPassword=(your database user password)
  • jcr.DbPassword=(your database user password)
  • likeminds.DbPassword=(your database user password)
  • feedback.DbPassword=(your database user password)

If you do not want these password values removed after every run, make sure PWordDelete=false is set in (wp_profile root)/ConfigEngine/properties/wkplc.properties.

Note

If your server is configured with database runtime users, for example, `feedback.DbRuntimeUser=(your feedback database runtime user)`, make sure to set their password values correctly (for example, in `feedback.DbRuntimePassword=(your feedback database runtime user password)`).

In a Helm-based deployment, moving from one cumulative fix (CF) to another one is also handled through Helm upgrade. In addition to the Prerequisites mentioned, the following actions are recommended when applying cumulative fixes:

  • Back up the file system of the persistent volumes associated with the namespace. Also, take a matching backup of the database associated with the Core pod.
  • If you are running a 24/7 environment, it is recommended to set up a blue/green deployment before applying a CF to ensure high availability. While DX Core stays available with multiple pods, DAM is not highly available during CF application. See the topic Difference and Similarities Between Traditional and Kubernetes DX Deployments that shows how a DX solution could be deployed for high availability and blue/green deployments in a single Kubernetes cluster.
  • Before upgrading, temporarily set the DAM staging interval to 1440 (24 hours) using the dxclient manage-dam-staging trigger-staging command or adjust the cycleLength to 1440 using the DAM REST API StagingController.updateSubscriberData. Alternatively, you can disable DAM Staging while the publisher (source) and the subscriber (target) are not yet on the same CF version but note that reestablishing staging restages all assets.
  • (Optional) Consider disabling WCM Syndication from and to the current environment.

Helm Upgrade configuration command

After making the needed changes to your custom-values.yaml file, use the following command:

# Helm upgrade command
helm upgrade -n your-namespace -f path/to/your/custom-values.yaml your-release-name path/to/hcl-dx-deployment-vX.X.X_XXXXXXXX-XXXX.tar.gz
  • The your-namespace is the namespace in which your HCL Digital Experience 9.5 deployment is installed and your-release-name is the Helm release name you used when installing.
  • The -f path/to/your/custom-values.yaml parameter must point to the custom-values.yaml you have updated.
  • The path/to/hcl-dx-deployment-vX.X.X_XXXXXXXX-XXXX.tar.gz is the HCL Digital Experience Helm Chart that you extracted in the preparation steps.