Upgrading Appian on Kubernetes

Overview

The following describes how to upgrade to new versions of Appian on Kubernetes for self-managed customers. This includes upgrades to both the Appian operator and the Appian images.

Download new artifacts

Download the new Appian operator Helm chart, pull the new Appian operator and Appian container images, and push the new images to your organization's registry.

Upgrading both the Appian operator and Appian images

To upgrade both the Appian operator and Appian images at the same time, you would:

Follow the steps in Upgrading the operator.
Follow the steps in Upgrading Appian component images.

Upgrading the operator

Caution: Starting with version 0.156.0, a new license file will be required to start the operator. For more information about requesting and importing the license file, see the Installing Appian on Kubernetes page.

Upgrading the Appian operator is as simple as running helm upgrade:

helm --namespace appian-operator upgrade appian-operator appian-operator-<APPIAN_OPERATOR_VERSION>.tgz \
   --reset-then-reuse-values \
   --wait

Note: If you have restricted the Appian operator's cluster-wide access and installed the operator's controllers in additional namespaces, repeat this step once for each namespace - substituting --namespace appian-operator with --namespace <NAMESPACE>.

If you have any trouble upgrading the operator, see Troubleshooting Appian on Kubernetes.

Upgrading the Appian images

The following steps will upgrade the component images of the Appian site including webapp, data-server, and other components. This is typically done when there are new features released.

Stop your Appian site.
Within the Appian CR, for each component, update the .spec.[COMPONENT].image.tag field to be the new version of the image.
Restart your Appian site.

If you have any trouble upgrading Appian, see Troubleshooting Appian on Kubernetes.

Feedback

Was this page helpful?