Appian on Kubernetes

Appian on Kubernetes lets self-managed customers host Appian as a containerized application on a Kubernetes cluster. Instead of managing each Appian component separately, Kubernetes orchestrates them together—and the Appian operator handles the coordination so you don't have to.

Key benefits

Appian on Kubernetes provides:

• Resilience. If a component goes down, Kubernetes detects the discrepancy and spins up a replacement automatically.
• Scalability. Pod replicas can scale up to meet demand. For example, if CPU load on the web server spikes, Kubernetes can automatically add replicas.
• Simplified management. All Appian components are managed through a single custom resource configuration file, giving you one place to configure and control your deployment.
• Operator-driven automation. The Appian operator handles the complex sequencing required to start, stop, and maintain Appian components—you define the desired state, and the operator reconciles it.

Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close

How Appian on Kubernetes works

Appian runs using various components: application server, search server, data server, and others. On Kubernetes, each component runs as a pod. The Appian operator—built on the operator pattern—watches over those pods and continuously works to keep the actual state of the cluster aligned with your desired configuration.

You define your Appian installation using a single custom resource (CR) configuration file. The operator reads that file and manages all the underlying Kubernetes resources for you.

For a deeper look at the system architecture and platform-specific diagrams, see Architecture: Appian on Kubernetes.

Browsing these pages

This browser is organized into the following sections:

• Getting Started: System architecture, reference diagrams, and step-by-step instructions for installing, migrating to, and upgrading Appian on Kubernetes.
• Configuration: Configuration reference material for the Appian custom resource, custom resource definition, Helm chart values, artifacts, certificates, and pod autoscaling.
• Reference: Release notes for the Appian operator and the Appian on Kubernetes migration tool.

Additional configuration topics for self-managed Appian environments are located in the Self-Managed Server Administration browser, including post-install configuration, security, high availability, backups, and troubleshooting.

Get started

If you're new to Appian on Kubernetes, start with the architecture overview to build a mental model of how the system works, then follow the installation guide to set up your first deployment.

For answers to common questions, see the FAQ: Containerized Self-Managed Appian.

Feedback