Upgrade SignServer Helm Deployment

Helm offers a streamlined way to modify deployment parameters and upgrade to newer versions. The following sections provide steps needed to ensure a smooth upgrade process, from updating configuration parameters to upgrading to a new release version.

Upgrade Instructions

Make sure to always back up your database before starting the upgrade process. In case you need to roll back an upgrade, you can restore the database backup and re-deploy the previous Helm Chart version.

As of SignServer 7.6.0, SignServer container images are built with default allowlists. For more information on the allowlists, see Deploy-time Configuration.

Update Helm Chart Values Files

Review the SignServer Upgrade Notes for any changes that might need to be introduced to your Helm chart's values files and update the files accordingly.

Upgrade to the New Helm Chart Version

Use your Helm Chart values file with the new chart version to upgrade an SignServer deployment:

helm upgrade <deployment-name> -f signserver-values.yaml \
    oci://repo.keyfactor.com/charts/signserver --version <new-version>

Update Parameters for an Existing Release

To modify SignServer deployment parameters, you can use the helm upgrade command to update parameters for an existing release.

For example, if you initially deployed SignServer with the parameter services.proxyHttp.httpPort set to 8081, and now want to change it to 8888, adjust the value in the chart values file and run the helm upgrade command using the same values file and chart version.

Modify the property in the chart value file, for example, signserver-values.yaml:

services:
  proxyHttp:
    httpPort: 8888

After running the upgrade command, Helm will identify the affected Kubernetes resources and redeploy them with the new configuration.

For more complex upgrades, you can use multiple values files, adding --set and --reuse-values flags, and so on. For more more, refer to the Helm Upgrade documentation.