FAQ: Containerized Self-managed Appian

This page answers questions that are commonly asked about Appian on Kubernetes (AOK).

When and why

Which self-managed environments are supported?

Starting with Appian 25.4, Appian can only run in self-managed environments using containers managed by Kubernetes. In Appian 25.4 and later, no Windows or Linux installers or hotfixes will be available for download. Only AoK installers and hotfixes will be available.

Appian 25.3 is the last version that supports non-containerized deployment. Hotfixes for 25.3 will be published as both containerized and non-containerized deployments for its full support lifetime.

If I'm running an earlier version of Appian in a self-managed deployment, do I have to migrate to Appian on Kubernetes?

No. Self-managed environments running Appian 25.3 or earlier will receive hotfixes for that version's full support lifetime. However, you won't be able to upgrade your environment to 25.4 or later without migrating to either AoK or Appian Cloud.

Why is Appian doing this?

Appian Cloud now runs on a Kubernetes infrastructure, and all future features for the platform are built with that in mind. We want to have one path to success for Appian Cloud and self-managed customers. Kubernetes unlocks some of the features we are most excited to deliver, such as Autoscale for Processes.

What can I do to prepare?

Share the Appian on Kubernetes documentation with DevOps, Platform, or Cluster administrators in your business to understand how best to stand up a vendor application running on Kubernetes.

If you have additional questions, you can submit them here.

Platform support

Can I run Appian "on containers" or virtual machines (VMs) without Kubernetes?

No. Kubernetes and the Appian Operator are the only supported ways to run Appian in a containerized fashion.

What platforms do you support for AoK?

See the list of supported platforms in the AoK installation guide.

I'm an OpenShift customer. Is Appian Red Hat Certified and present in their official Catalog?

Yes. Appian can be found in the Red Hat Ecosystem Catalog.

Do I have to use a Kubernetes Operator?

Yes. The Appian Operator exists to ensure the orderly startup, management, and shutdown of an Appian instance, and coordinates it all. To ensure a good experience, we use an Operator instead of 'just' a Helm Chart.

What do I have to bring myself?

• A Kubernetes cluster running a supported version.
• A relational database, new or old.
  • Drivers and Kubernetes init containers if you're using Aurora MySQL, MySQL or IBM Db2.
• Domain name.

Scaling

Does Appian on Kubernetes enable full "elastic scale?"

No, aside from the Appian Operator itself and httpd, we don't have elasticity for other components of Appian.

What we do have:

• Horizontal Pod Autoscaling (scaling number of pods based on CPU usage) for the Apache Web Server (httpd).
• Vertical Pod Autoscaling (scaling resource allocation for pods based on usage) for the Appian Operator and its components themselves.

We plan on having this kind of scalability in the future. AoK will enable it down the road.

Is Autoscale available for AoK?

No. While we do ultimately want to bring Autoscale to Appian on Kubernetes, it's not currently available.

Cluster and resource sizing

How should I plan for what resourcing your components need in my cluster?

Suggestions are covered by our documentation but these are only a starting point, as your usage of Appian may influence which Appian components are used more than others.

Staffing and Support

Is Appian on Kubernetes fully supported?

Yes, Appian on Kubernetes is supported for production usage, and gets hotfixes and major versions just like any other deployment method.

What kind of people or teams at my company will be the right people to talk to about this?

Your existing infrastructure team(s) will be able to help you start a conversation about (if you have) a Kubernetes cluster and what requirements surround deploying a new application onto it.

Security

Is Appian on Kubernetes safe and secure?

Yes. Appian on Kubernetes is held to the same standards as any other way of deploying that we provide. The container images that make up AoK are the same ones we use internally on our own cloud environments, are scanned and hotfixed for CVEs regularly, and are hardened against applicable DISA STIGs.

Can Appian be restricted in my cluster in terms of networking and namespacing?

Yes, you have control over network interactions between Appian and anything outside your cluster or within it.

Feedback