Continental Innovates with Rancher and Kubernetes
The purchase and use of Rancher products and services are governed by an Enterprise Agreement
including an End User License Agreement and the applicable Product Appendix(ces) which includes
Exhibits for those Rancher products and services. For Order Forms dated prior to April 1, 2020,
where a Rancher Enterprise Agreement has not been signed, go here
to find the Rancher End User License Agreement.
Support for Rancher Labs products is offered under two subscription plans:
Standard and Platinum. Rancher Labs Support Services are only
for companies with an active subscription to one of these plans. A company (the “Customer”) may
purchase Support Services through one of these plans from the Rancher Labs sales department.
Once purchased, a Rancher representative will activate the Customer in the Rancher Labs Support
Portal system, which will enable the Customer to obtain technical support at the appropriate
level of service.
These Terms of Service will be updated periodically. For example, as new releases become
Generally Available, the End of Maintenance and End of Service dates will be refreshed, and new
products may be added, and older products may be modified or deleted from the Rancher Support
Matrix. Please refer back to this page periodically for the current terms.
The Rancher Labs SLA is defined in terms of initial response time after a Customer files a
support ticket. Rancher Labs has defined 4 severity levels under which tickets can be filed
(depending on the level of support purchased), described in the table below:
The Customer will provide an initial severity level associated with a ticket. The Rancher Labs
Support Manager will determine, in Rancher’s sole discretion, if the ticket was correctly
classified and may increase or decrease the assigned severity level. Response times, per plan,
are shown in the table below, for each severity level:
† or as agreed upon
†† Time zone options for business day/hour selection: San Francisco (US Pacific,
default), Amsterdam (CET), Shenzhen (CST), Sydney (AET)
The date that signifies when a Customer may purchase a support plan for a new product release
from Rancher Labs that is tagged “Stable”.
Note: Support plans are only for published product releases that are tagged “Stable”. Any
product release with the “Latest” tag is meant solely for open source community users and not
covered by a support plan from Rancher Labs.
The date that signifies when a specific product release will have no further code-level
maintenance other than security-related updates deemed critical by Rancher Labs. Security issues
could be related to publicly identified security vulnerabilities or privately by Rancher Labs
and its ecosystem partners.
The date after which neither security-related maintenance builds, nor technical support through
Rancher Labs, will be available for a product release.
"Major Releases" (X.y.z) deliver major features and enhancements. They are not guaranteed
backwards compatible with any previous Major Release.
“Minor Releases” (x.Y.z) deliver minor feature developments, enhancements to existing features,
and bug fixes. They incorporate all applicable fixes made in prior minor and maintenance
"Maintenance Releases" (x.y.Z) deliver bug fixes that are severely affecting a number of
customers and cannot wait for the next major or minor release. They incorporate all applicable
fixes made in prior maintenance releases.
SLAs only apply to Rancher products found in the chart below with their corresponding phases of
Upon the General Availability date, products are supported and maintained until
the End of Maintenance date.
After a product release reaches its End of Maintenance date, no further
code-level maintenance will be provided, except for critical security- related
fixes on a per-request basis.
After the EOM date, Software will continue to be supported until it reaches
its End of Life date, in the form of:
Once a product release reaches its End of Life date, the customer may continue to
use the product within the terms of product licensing agreement.
Support Plans from Rancher Labs do
not apply to product releases past their EOL date.
Rancher products may be distributed with certain “open source software” or “free software”
(“Open Source Software”) or contain open source integrations with other software. Open Source
Software and integrations covered by Rancher SLAs, for each supported version of a Rancher
product, are those validated and certified per support matrix00 below.
Note: Rancher RKE Downstream clusters can be either provisioned by node drivers or custom/existing nodes, or registered into Rancher.
Note: Windows clusters use a mix of Linux and Windows hosts as cluster nodes. Windows nodes can only be used for deploying workloads, while Linux nodes are required for cluster management.
Note: Rancher K3S clusters can only be registered into Rancher.
Note: Rancher RKE2, also known as RKE Government, clusters can only be registered into Rancher.
Note: Hosted Kubernetes clusters can be either provisioned by Rancher or registered into Rancher.
Note: Any Upstream Kubernetes conformant cluster can be registered.
Click here for all supported versions
† All “latest” tagged releases are intended for the Rancher community users to test-drive a new release and provide feedback. These “latest” tagged releases whilst covered by Rancher SLA are not generally meant for production use cases. Kindly use only the “stable” tagged releases for your own production use cases.
0 For open source components not listed in the matrix above, support is limited to troubleshooting for root cause up to Rancher’s drivers and interfaces to those components. Root causes that are identified to be beyond this limit will need to be pursued by Company with the maintainers and providers of commercial support for those components.
00 for ensuring best support and clarity on supportability, Company is recommended to publish to Rancher a list of components that are critical to its deployment but not not explicitly called out in the support matrix
1 certified on default OS kernel. Issues resulting from third party tools (typically, for reasons such as security) interfering with Docker or other necessary system calls are deemed resolved should disabling such tools restore functionality
2 certified configurations are based on default settings of individual components. Where Company has deviated from certified configurations, Rancher Labs reserves the right to recommend the Company to revert to a certified configuration to resolve the reported issue.
3 whilst running kubernetes clusters in uncertified configurations may be possible, it is not recommended
4 upgrade of any individual component to a different version is likely to result in system downtime
5 changes to default settings of individual components may be necessary on exceptional basis, for reasons such as fine tuning for performance and scale. Engagement with Rancher Consulting or a partner may be recommended.
6 SLA on node drivers is limited to those that are built-in and active by default when Rancher is installed
7 SLA does not apply to issues within an application and its lifecycle management
8 issues may be referred to the partner as appropriate
‡ SLA is limited to running workload clusters on hosted kubernetes provider and does not apply to running the Rancher control plane on one of the listed hosted kubernetes providers for all Rancher versions older than Rancher v2.5.x. In Rancher v2.5.x, SLA applies to running Rancher control plane on the listed kubernetes distributions and hosted providers.
Rancher occasionally deprecates features for various reasons. Reasons for deprecation could include a feature being updated or replaced by a new implementation, a new feature set, upstream technology is no longer available or has made incompatible changes, etc.
When a feature is deprecated, Rancher will aim to follow the steps outlined in the table below:
Notification that a feature is deprecated will be announced in the Rancher release notes. Visual queues will appear in the UI indicating which feature is deprecated and suggest a replacement (if there is one).
In the release where deprecation is announced, users can expect the feature to be available and supported. Upgrading from a previous Rancher version to this release is supported. Upgrading to a release where the feature is EOL without migrating from or disabling the feature beforehand is not supported. Upgrading to a release where the feature is EOL without first disabling the functionality could cause a situation where Rancher is broken or inoperable. It is very important to check the release notes and discuss your plans with your Customer Success Manager before each upgrade.
During the deprecation period, Rancher will maintain the deprecated functionality on a best effort basis. In some cases, updates might no longer be available upstream or incompatible changes with the existing functionality might prevent Rancher from being able to provide updates or bug fixes to the feature. During the deprecated release lifecycle, users can still open issues and file bugs against the features.
In a major release, there will be major changes to product functionality, features, and behaviors. There is no guarantee that these changes are backward compatible or offer similar functionality. Features that have been dropped, deprecated or altered will be documented in the release notes.
There might be circumstances that do not fit into this policy document. Such situations will be evaluated and discussed with stakeholders. All deprecation notes, including those by exceptions, will be included in the Release notes for the release.
A ticket means a discrete technical or non-technical issue that is submitted by Company to
Rancher Labs that requires a response as specified below in this document. A ticket exists in
the Rancher Labs Support Portal and includes all the communication associated with the issue.
Rancher Labs provides a full featured, web-based ticket management system that has numerous
features and capabilities. The support portal is available to Company of any support tier 24×7
and is the primary method for ticket submission. The support portal allows Company to enter
tickets, add information to existing tickets, receive information and updates about tickets,
close tickets, and list their currently open and closed tickets.
Customizations are defined to include any changes to the original source code, including but not
limited to changes to the User Interface, the addition or modification of adapters such as for
authentication, VM or server provisioning, deploying the software (e.g., the management server)
on operating system or Docker versions that are not certified by Rancher Labs, and altering the
scripts and byte code included with the product. Customizations to this software may have
unintended consequences and cause issues that are not present with the original, unmodified
software. As a result, it is Rancher Labs policy that any bugs, defects or other issues that are
present in areas of the product that the Company has altered must be reproduced by the Company
on an unmodified system prior to the submission of a support case or bug report. Additionally,
the Company is required to state all customizations present on the system when submitting a
The Rancher Labs Support Manager is available to discuss cases that have gone unresolved for an
amount of time deemed unsatisfactory by the Company. We hope you are satisfied with the support
you have contracted for and that your organization’s needs are addressed promptly. However,
Rancher Labs recognizes that there may be times when additional attention or assistance is
required. Upon request, the Support Manager will provide the Company with contact information
for the Vice President of Engineering or the Vice President of Customer Success to discuss
issues that the support team has been unable to resolve for some time or that were resolved in
an unsatisfactory manner.
In the event Company terminates or elects not to renew Support Services for any Licensed Software
Product licensed by Company, Company may continue to use such Licensed Software Product pursuant
to this Agreement but will have no further right to Support Services for such Licensed Software
In the event that Company does not renew the Support Services term and the Support Services
lapse, Company may reinstate the Support Services at the then-current annual rate by providing
written notice to Rancher Labs and paying a reinstatement fee equal to the then-current
equivalent daily Support Services rate multiplied by the number of days between the date of
expiration of the previous Support Services term and the date of renewal of the Support
In the fulfillment of Rancher Labs Support Services obligations, Rancher Labs may require actual
or remote access to the Licensed Software Product and/or the systems on which the Licensed
Software operates. With Rancher Labs’ assistance, Company agrees to provide any such access and
other assistance reasonably requested by Rancher Labs. Company agrees that providing such access
and assistance is a condition to Rancher Labs’ obligation to provide Support Services under this