Release cadence and support cycle

Mirantis aims to release Mirantis OpenStack for Kubernetes (MOSK) software regularly and often.

MOSK software includes OpenStack, Tungsten Fabric, life-cycle management tooling, other supporting software, and dependencies. Mirantis’s goal is to ensure that such updates are easy to install in zero-touch and zero-downtime fashion.

MOSK major and patch releases

MOSK release cadence consists of major, for example, MOSK 23.1, and patch, for example, MOSK 23.1.1 or 23.1.2, releases. The major release with the patch releases based on it are called a release series, for example, MOSK 23.1 series.

Major release versions contain new functionality as well as bug and security fixes while patch release versions include only fixes for security vulnerabilities and product known issues.

Patch releases aim to significantly shorten the cycle of CVE fixes delivery onto your MOSK deployments to help you avoid cyber threats and data breaches.

Content	Major release	Patch release
Version update and upgrade of the major product components including but not limited to OpenStack, Tungsten Fabric, Kubernetes, Ceph, and Stacklight 0
Container runtime changes including Mirantis Container Runtime and containerd updates
Host machine changes including host operation system updates and upgrades, kernel updates, and so on
Changes in public API
Changes in the Container Cloud and MOSK lifecycle management including but not limited to machines, clusters, Ceph OSDs
Fixes for Common Vulnerabilities and Exposures (CVE)
Fixes for known product issues

0

StackLight subcomponents may be updated during patch releases

When updating to a patch release version, there is no impact on a cluster expected as long as lightweight changes included in the patch release content require only containers restarts on the cluster.

Each subsequent major release includes patch release updates of the previous major release.

You may decide to update between only major releases without updating to patch releases. In this case, you will perform updates from an N to N+1 major release. However, Mirantis recommends applying security fixes using patch releases as soon as they become available.

You can skip a number of patch releases and update to the latest one. Though, if between the two major releases you apply at least one patch release belonging to the N series, you should obtain the last patch release in the series to be able to update to the N+1 major release version.

See also

• Update a MOSK cluster to a patch release version New

• Update a MOSK cluster to a major release version

OpenStack support cycle

Mirantis provides Long Term Support (LTS) for specific versions of OpenStack. LTS includes scheduled updates with new functionality, bug and security fixes. Mirantis intends to introduce support for new OpenStack version once a year. The LTS duration of an OpenStack version is two years.

The diagram below illustrates the current LTS support cycle for OpenStack. The upstream versions not mentioned in the diagram are not supported in the product as well as the upgrade paths from or to such versions.

Versions of Tungsten Fabric, underlying Kubernetes, Ceph, StackLight, and other supporting software and dependencies may change at Mirantis discretion. Follow Release Compatibility Matrix and product Release Notes for any changes in product component versions.

See also

Operations Guide: Upgrade OpenStack

Technology Preview features

A Technology Preview feature provides early access to upcoming product innovations, allowing customers to experiment with the functionality and provide feedback.

Technology Preview features may be privately or publicly available but neither are intended for production use. While Mirantis will provide assistance with such features through official channels, normal Service Level Agreements do not apply.

As Mirantis considers making future iterations of Technology Preview features generally available, we will do our best to resolve any issues that customers experience when using these features.

During the development of a Technology Preview feature, additional components may become available to the public for evaluation. Mirantis cannot guarantee the stability of such features. As a result, if you are using Technology Preview features, you may not be able to seamlessly update to subsequent product releases, as well as upgrade or migrate to the functionality that has not been announced as full support yet.

Mirantis makes no guarantees that Technology Preview features will graduate to generally available features.