Version Policy

DC/OS version lifecycle and compatibility matrix

The Version Policy page was updated on October 21, 2019.

Mesosphere DC/OS Version Lifecycle and Compatibility Matrix

This page explains to Mesosphere customers, partners, users, and operators of Mesosphere DC/OS the modifications or enhancements to the same software product as designated by a change in the version release. A version release provides backward compatibility to all released APIs. The guidelines outlined in this document applies to the version of DC/OS and its catalog packages.

DC/OS Version Lifecycle

Mesosphere tests DC/OS Enterprise with specific components and operating systems as covered in the DC/OS Version Compatibility Matrix. This testing is provided in the DC/OS Platform Interoperability Matrix. Support services for customers under a license and support agreement is defined within the Mesosphere Support Terms.

Versioning Definitions

• Major Versions (X.y.z) are releases for providing major and minor features and improvements or optimizations to existing features. They incorporate all applicable bug fixes made in earlier Major, Minor, and Maintenance versions.
• Minor Version (x.Y.z) are versions for delivering minor features, improvements or optimizations to existing features, and bug fixes. They incorporate all applicable bug fixes made in earlier Minor versions, and Maintenance versions.
• Maintenance Version (x.y.Z) are versions for providing bug fixes that are highly impactful to a number of customers and who cannot wait for the next Major or Minor version. They incorporate all applicable bug fixes made in prior Maintenance versions.
• “End of Life (EOL)” versions are no longer supported by Mesosphere, upgrading to a later version is highly recommended.

Version Lifecycle

Mesosphere shall provide support services for customers under a current agreement as outlined in the Mesosphere Support Terms, for specific versions of Mesosphere DC/OS. While these versions are outlined in the Mesosphere DC/OS Version Compatibility Matrix they follow a specific model for determining which versions are supported. The model follows an N-2 (for Major and Minor Versions) and N-4 (for Maintenance Versions) specification. Thus, Mesosphere shall provide support services for those versions of DC/OS that are either the current, N, or up to two Minor versions behind.

Examples of Major and Minor versions are as follows:

• Major Version: Upon the availability of a new DC/OS Major version, 2.0.0, Maintenance versions prior to (N-2) Minor versions of the previous (N-1) major release would not be supported. Major Versions also count towards advancing the Minor number version.

Thus, upon the release of 2.0.0 where 1.13.4 and 1.12.5 are available:

• Minor Versions 1.13.2 (1.13.4 and - 2) would be supported, while older versions (1.13.1) would no longer be supported.

• Minor Versions 1.12.3 (1.12.5 and - 2) would be supported, while older versions (1.12.2) would no longer be supported.

• Minor Version: Upon the availability of a new DC/OS Minor version 1.11.0, minor versions prior to and including 1.8.0 will no longer be supported as (N-2) includes 1.11 (N), 1.10 (N-1) and 1.9 (N-2).

• Maintenance Version: Upon the availability of DC/OS Maintenance version 1.10.5, Maintenance versions prior to and including 1.10.0 will no longer be supported as (N-4) includes 1.10.5 (N), 1.10.4 (N-1), 1.10.3 (N-2), 1.10.2 (N-3) and 1.10.1 (N-4).

DC/OS Platform Version Compatibility Matrix

DC/OS will run on the tested platform components and operating environments. The list of support matrix for platform components and operating environments are as follows:

CentOS support matrix

RHEL support matrix

Oracle Linux support matrix

Ubuntu support matrix

Customers running DC/OS on non-supported platform components should upgrade to a supported component. For clarity, Mesosphere only provides support services to paying customers under a written agreement. The term “supported” in Mesosphere documentation refers to whether the indicated software component has been tested for compatibility.

CentOS support matrix

RHEL support matrix

Ubuntu support matrix

Oracle support matrix

CoreOS support matrix

NOTE: Starting with DC/OS 2.0, we have discontinued support for CoreOS and have ceased qualifying it as an Operating System. This chart shows the final qualified versions of DC/OS for the final qualified versions CoreOS.

Web Browser and CLI Matrix

Use the following legend table to see the supported/not supported service for the operating environments on which DC/OS has been tested.

Legend for Web Browser and CLI support matrix

Web Browser support matrix

CLI support matrix

NOTE: CoreOS 1800.7.0 requires DC/OS version 1.11.6 or later.

Customer Advisory for CentOS/RHEL 7.X

IMPORTANT: Docker recently enabled kmem accounting in version 17.06+. Customers may notice instability for the entire system when running under RHEL or CentOS 7.x. The symptoms include tasks getting stuck indefinitely and kernel-related error messages in the system logs. The kmem accounting feature in Redhat’s forked Linux Kernel is incomplete and can cause kernel deadlocks or kernel memory leaks. Details on the bug and mitigation instructions are located here.

NOTE: Because of the kmem bug, Mesosphere only supports Kubernetes on DC/OS with CentOS/RHEL 7.X when using DC/OS 1.12 or later and CentOS/RHEL 7.5.

Version Compatibility Matrix

Mesosphere maintains and certifies several packages for DC/OS.

Base Technology

Mesosphere does not offer support services for the base technology (for example, Jenkins). The base technology version is denoted as the second version in the package number (for example, 1.2.3-4.5.6).

Certified Package Designations

Services that are labeled as “Certified” have been tested by Mesosphere for interoperability with DC/OS, but Mesosphere disclaims all warranties, and makes no promises, including with respect to the services’ operation or production readiness. Support for the integration may be available from Mesosphere or the creator of the service. The matrix below lists certified packages and the current state of which packages are tested on what version of DC/OS, and what is within the best effort scope of our technical support organization.

The designations are as follows:

⚫ This combination is tested and compatible with the specified version of DC/OS.

• This package is within the scope of our technical support organization.
• This is package is eligible for bug fixes.

◒ This combination has been tested previously and should be compatible with the specified version of DC/OS.

• This combination is not within the scope of our technical support organization.
• This combination is not eligible for bug fixes.

◯ This package combination has not been tested.

• This combination is not within the scope of our technical support organization.
• This combination is not eligible for bug fixes.

Certified Packages and DC/OS Versions

Beta Package Designations

Services that are labeled as “Beta” are not ready for production.

The designations are as follows:

◯ - This package combination has not been tested.

• This combination is not within the scope of our technical support organization.
• This combination is not eligible for bug fixes.

B - This package combination is beta.

• Beta packages are not within the scope of our technical support organization.
• Beta packages iterate quickly and are not eligible for bug fixes.

Beta Packages and DC/OS Versions

Footnotes

• ¹ Beta DC/OS Storage Services 0.5.1 requires DC/OS 1.12.1 or later.
• ² Package maintained and supported solely by DataStax Corporation.