About Versions in a Chart.yaml File

Each chart contains metadata in its Chart.yaml file.

As an example, let's look at the Chart.yaml file for the ttoperator chart. In particular, let's look at the appVersion and version metadata.

apiVersion: v2
name: ttoperator
description: A Helm chart for Kubernetes

# A chart can be either an 'application' or a 'library' chart.
#
# Application charts are a collection of templates that can be packaged into versioned archives
# to be deployed.
#
# Library charts provide useful utilities or functions for the chart developer. They're included as
# a dependency of application charts to inject those utilities and functions into the rendering
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
type: application

# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 2211340.1.0

# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application. Versions are not expected to
# follow Semantic Versioning. They should reflect the version the application is using.
# It is recommended to use it with quotes.
appVersion: "22.1.1.34.0"

The value of version reflects the TimesTen release number without dots (.) followed by .1.0. For example, for release 22.1.1.34.0, the value of version is 2211340.1.0.

Similarly, the value of appVersion reflects the TimesTen release number, but is in a different format. For example, for release 22.1.1.34.0, the value of appversion is 22.1.1.34.0.