Information
  • Author: Appian Corporation
  • Type: Utility
  • Support: This plug-in or utility is not supported by the author. The content is free to use with a licensed product, but it is made available as-is and Community supported.
  • Compatible Version(s): 25.1
  • First Released:
  • Last Updated:
  • Cost: Free
Resources
Share
Home » AppMarket » Appian Platform Helm Chart

Appian Platform Helm Chart

Overview

A Helm chart (appian-platform-cs) for deploying Appian on Kubernetes (AoK) sites with templated support for common configuration options and baked-in best practices. This chart deploys a single custom resource of type `appian` that is managed by the Appian Operator.

Key Features & Functionality

  • Simplified specification of common configuration options including data sources, high availability, SMTP, replication and ingress.
  • Configure numerous sizing parameters across all Appian components from built-in sizing templates by simply specifying a T-Shirt size.
  • Built-in best practice configurations.
  • Supports all fields from the Appian platform Custom Resource Definition for overriding any templated configurations.
  • Helm chart can either be used simply to generate the required Appian Custom Resource yaml spec (using `helm template`), or to directly deploy an Appian Custom Resource to your cluster (using `helm install`).
Anonymous
Parents

  • v1.1.0 Release Notes

    • Minor increase to Search Server CPU requests for Small and Medium t-shirt sizes in-line with public docs update.
    • Added `dataServer.class` field to enable independent scaling of the Data Service component without changing global t-shirt size.
    • Breaking Change Aligned Data Service t-shirt sizing with latest public docs. This keeps resources relatively similar to earlier versions, but reduces RTS count for each t-shirt size. Use the new `dataServer.class` field or the `dataServer.rts.count` field to readjust if required.
    • Breaking Change CPU limits are no longer set by default. This is to align with K8s best practices (where accurate CPU limits for the specific usage scenario are not already known). CPU limits can be applied by setting the new field `disableCpuLimits` to `false` (it defaults to `true`). If enabled, the t-shirt size's CPU limits are applied. This can be overridden globally by setting the new field `defaultCpuLimits` or overridden per component by setting `[component].cpuLimits`. The field `workerNodeTotalCpu` has been removed in favour of `defaultCpuLimits`. Previous chart behaviour can be achieved by setting `disableCpuLimits` to `false` and setting `defaultCpuLimits` to the previous value of `workerNodeTotalCpu`.
    • Breaking Change Removed `serviceManager.cpuLimits` and `serviceManager.memoryLimits` fields. Use `serviceManager.default.cpuLimits` and `serviceManager.default.memoryLimits` instead.
    • 'disableResourceRequests` now sets no `resources.requests` at all, rather than incorrectly setting them to `0`.
    • Deprecated `dataSources.mysqlDriverConfigMapName`, which enabled deploying the MySQL driver via a ConfigMap and webapp init container. The supported MySQL driver is now too large to be mounted via a ConfigMap.
    • Built against Appian operator v0.173.0 and Appian platform 25.1. This chart will work with other versions of the Appian operator and platform, both older and newer, but some parameters may not be valid
Comment

  • v1.1.0 Release Notes

    • Minor increase to Search Server CPU requests for Small and Medium t-shirt sizes in-line with public docs update.
    • Added `dataServer.class` field to enable independent scaling of the Data Service component without changing global t-shirt size.
    • Breaking Change Aligned Data Service t-shirt sizing with latest public docs. This keeps resources relatively similar to earlier versions, but reduces RTS count for each t-shirt size. Use the new `dataServer.class` field or the `dataServer.rts.count` field to readjust if required.
    • Breaking Change CPU limits are no longer set by default. This is to align with K8s best practices (where accurate CPU limits for the specific usage scenario are not already known). CPU limits can be applied by setting the new field `disableCpuLimits` to `false` (it defaults to `true`). If enabled, the t-shirt size's CPU limits are applied. This can be overridden globally by setting the new field `defaultCpuLimits` or overridden per component by setting `[component].cpuLimits`. The field `workerNodeTotalCpu` has been removed in favour of `defaultCpuLimits`. Previous chart behaviour can be achieved by setting `disableCpuLimits` to `false` and setting `defaultCpuLimits` to the previous value of `workerNodeTotalCpu`.
    • Breaking Change Removed `serviceManager.cpuLimits` and `serviceManager.memoryLimits` fields. Use `serviceManager.default.cpuLimits` and `serviceManager.default.memoryLimits` instead.
    • 'disableResourceRequests` now sets no `resources.requests` at all, rather than incorrectly setting them to `0`.
    • Deprecated `dataSources.mysqlDriverConfigMapName`, which enabled deploying the MySQL driver via a ConfigMap and webapp init container. The supported MySQL driver is now too large to be mounted via a ConfigMap.
    • Built against Appian operator v0.173.0 and Appian platform 25.1. This chart will work with other versions of the Appian operator and platform, both older and newer, but some parameters may not be valid
Children
No Data
© 2025 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.