Appian Platform Helm Chart

v2.0.0 Release Notes

• BREAKING CHANGES - This release includes breaking changes. If upgrading to this version of the Helm chart, read the full Release Notes from the downloaded README (pdf/html) carefully before upgrading and use `helm tempalate` to compare the output with that from your current version to ensure the result is as expected.
  
  
• The minimum Appian Operator version compatible with this chart is v0.194.0.Restructured or renamed some existing chart values fields to align with a more standardised naming approach (see reference table in full release notes).
• Corrected data source template for Oracle connection URL
• Support setting `securityContext` globally for all components, or at component level as `[component].securityContext`.
• Support disabling the built-in Search Server init container that sets vm.max_map_count on the worker node
• Support setting `images.pullPolicy` to be applied to all components and built-in init containers.
• Removed support for deprecated `dataSources.mysqlDriverConfigMapName` field.
• Added default CPU and memory requests and limits to httpd
• httpd affinity rules updated to allow the n+1 httpd pod to run and terminate
• Support setting `spec.[component].serviceAccount` field for a component.
• The chart sets the custom property `server.conf.processcommon.AUTODELETE_ARCHIVES_DELAY_DAYS` to a default of 30 days
• Support OpenShift Default ingress controller as `ingressTemplate`.
• Chart now sets the new custom properties used by the Appian Data Service since 25.1
• The chart no longer populates `spec.httpd.nslookupImage` (which is not used from Operator v0.194.0).
• Data source username field `dataSources.[primary\|business[]].username` has been removed in favour of providing the username(s) via a secret
  
  
• Built against Appian operator v0.194.0 and Appian platform 25.4. This chart will work with older and newer versions of the Appian operator (to a minimum of v0.194.0) and Appian platform, but some parameters may not be valid.*

• Removed `searchServerPassword` field. From Operator v0.181.0, and Appian platform versions hotfixed from July 03, 2025 or later, the Operator now manages the Search Server password for you. Manually specifying a Search Server password is no longer required nor recommended. If you previously configured a Search Server password, you must remove this from your `passwords.properties` file when upgrading to this version of the Helm chart (see [this KB](community.appian.com/.../kb-2322-application-server-fails-to-start-due-to-improperly-configured-search-server-credentials for more details).
• Built against Appian operator v0.181.0 and Appian platform 25.3. This chart will work with older and newer versions of the Appian operator (to a minimum of v0.181.0) and Appian platform, but some parameters may not be valid.

• Fixed Search Server CPU requests for Medium t-shirt size to 200m.
• Built against Appian operator v0.178.0 and Appian platform 25.3. This chart will work with other versions of the Appian operator and platform, both older and newer, but some parameters may not be valid (e.g. `spec.rpa` was only introduced from v0.156.0).

Note there is a known issue with v1.1.1 using T-shirt size medium where CPU requests for Search Server defaults to an incorrect number. To work around this when using the medium T-shirt size, override the default search server CPU requests by setting the Helm value to 200m `searchServer.cpuRequests: 200m`. This issue will be corrected in the next version of the Helm chart.

• Fixed issue where `webapp.engineOverrides` field could not be set as it was incorrectly defined as an array instead of an object.
• Support setting `webapp.minHeapSize` to configure webapp's minimum heap size instead of using `customProperties`.
• 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

• Fixed issue where setting `disableResourceRequests: true` removed resource requests altogether but left limits in place, resulting in Kubernetes automatically adding resource requests back in and set to the same values as the limits. Now, setting `disableResourceRequests: true` sets resource requests to `0` to prevent this.
• 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

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

• Fixed an issue with the AGIC Ingress Template where an invalid `ingressClassName` was set. It now sets the annotation `kubernetes.io/ingress.class` instead, to the correct value, instead of setting `ingressClassName`.
• AGIC Ingress Template now defaults `ingressTemplate.usePrivateIp` to `false` instead of `true`.
• Built against Appian operator v0.166.0 and Appian platform 24.4. This chart will work with other versions of the Appian operator and platform, both older and newer, but some parameters may not be valid (e.g. `spec.rpa` was only introduced from v0.156.0).

• Allow storage.haSharedData to be specified when not in a high availability configuration
• No longer enforces passwordsPropertiesSecretName to be set (as this need only be provided and loaded at first environment startup)
• Support override of serviceManager.replicas in high availability configurations (from the default 3)
• Built against Appian operator v0.166.0 and Appian platform 24.4. This chart will work with other versions of the Appian operator and platform, both older and newer, but some parameters may not be valid (e.g. `spec.rpa` was only introduced from v0.156.0)

• Fixed bug preventing `ingress` from being used to completely override the templated ingress `ingressTemplate`
• Built against Appian operator v0.166.0 and Appian platform 24.4. This chart will work with other versions of the Appian operator and platform, both older and newer, but some parameters may not be valid (e.g. `spec.rpa` was only introduced from v0.156.0).