This section provides clear definitions of key terms to help you navigate and understand stack-related concepts.

• Accelerator automation

  Helm charts and automation scripts are distributed to clients, enabling them to deploy our software faster and easier.

• AMR (Annual Maintenance Release)

  Temenos builds, deploys, and commits software daily, which it accumulates and publishes as part of its regular release cycle. Updates are committed to the monthly build, which combines to form the Annual Maintenance Release (AMR) published in April of each year.

• Certification

  A certification tests specific software combinations through system setup and basic manual testing. The results are published, with notes and recommendations, in a certification document.

• Preferred

  We prefer clients to use the stacks we promote through our stack tables. From R23 onwards, we’ve arranged stacks in tiers, to indicate both shared features, and the level of testing and support infrastructure we offer.

• Recommended

  These are the stacks we recommend to clients. They’re tested every month, which means we’ve built up considerable expertise in their implementation. Runbooks, certifications and benchmarking reports form part of a rich support infrastructure for clients.

• Reference Architecture

  A reference architecture is a diagram that outlines the network components, software, and hardware requirements for deploying Temenos products in a specific stack. Updated annually as part of the AMR (Annual Maintenance Release), it provides a standardized framework to ensure consistent and efficient deployments.

• Runbooks

  Stack runbooks provide clear, step-by-step instructions, configuring, and deploying stacks. Runbooks ensure a smooth deployments experience for supported Temenos products or solutions within a specific target environment.

• Supported

  Supported means that these stacks are maintained for end-of-life issues only. For example, where an app server is no longer supported by the vendor.

• Technical Guides

  Technical Guides provide in-depth information about a particular software component, including installation and configuration procedures.

• Testing

  Testing includes the tests we carry out on every software build, as part of our CI / CD pipelines. It may also include formal certification or technical approval processes, where the stack undergoes a series of documented tests, from environment setup to COB and transaction testing (where applicable).

Kubernetes Support

Temenos supports N-2 Kubernetes releases in on-permise and cloud deployments, where N is the upstream Kubernetes release. If N-2 is not available on a specific cloud platform, you need to use N-3.

When a cloud vendor discontinues patches periodically, you need to move to the latest supported patch in a specific region. When a minor release is terminated (end of life), you need to upgrade to the latest available minor version - following the above support policy - to arrive at the version that should be used.

Example

The table shows examples of Kubernetes versions supported by Temenos on various clouds and/or platforms, as of May 2024

N = 1.30 (Upstream Kubernetes release)

OpenShift Support

Temenos supports all OpenShift releases that are under Full Support or Maintenance Support. For example, as of April 2024:

• OpenShift versions 4.15 and 4.14 are fully supported.
• OpenShift versions 4.13 and 4.12 are in Maintenance Support.

This means that at the particular date Temenos supports OpenShift versions 4.12 and higher. For more information, see Red Hat OpenShift Container Platform Life Cycle Policy.