This page details how to ensure Health Check runs properly for installations of Appian on Kubernetes.
Just like server-based, distributed installations of Appian require shared logs for Health Check, installations of Appian on Kubernetes require ReadWriteMany storage for Health Check.
Create a ReadWriteMany persistent volume claim in the same namespace as your Appian custom resource. For a list of in-tree volume plugins that support ReadWriteMany, see Access Modes. For a list of out-of-tree CSI volume plugins that do so, see Drivers (search for "Read/Write Multiple Pod").
A separate ReadWriteMany persistent volume claim must be created from the ReadWriteMany persistent volume claim(s) created when setting up High Availability.
Ensuring Health Check runs properly for your installation of Appian on Kubernetes is as easy as setting the
.spec.webapp.healthCheckExistingClaim field in your Appian custom resource:
# USER ACTION REQUIRED - Update to match the name of your ReadWriteMany persistent volume claim
Health Check for Appian on Kubernetes