Free cookie consent management tool by TermsFeed Health Check for Appian on Kubernetes [Appian on Kubernetes v0.156.0]
Page not found in the selected version; redirected to the home page.
Health Check for Appian on Kubernetes

Overview

This page details how to ensure Health Check runs properly for installations of Appian on Kubernetes.

How to set up Health Check

Create a ReadWriteMany persistent volume claim

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").

Note:  A separate ReadWriteMany persistent volume claim must be created from the ReadWriteMany persistent volume claim(s) created when setting up High Availability.

Configure your Appian custom resource

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:

1
2
3
4
5
6
7
8
apiVersion: crd.k8s.appian.com/v1beta1
kind: Appian
metadata:
  name: appian
spec:
  webapp:
    # USER ACTION REQUIRED - Update to match the name of your ReadWriteMany persistent volume claim
    healthCheckExistingClaim: ""
Open in Github Built: Thu, Jun 13, 2024 (05:06:58 PM)

Health Check for Appian on Kubernetes

FEEDBACK