Rancher v2.5.4

For this supported product version, open source software and integrations covered by our terms and conditions⁰ are those validated and certified per support matrix⁰⁰ below.

Installing Rancher v2.5.4 on RKE

RKE CLI & K8S for Local Cluster

OS & Docker

Installing Rancher v2.5.4 on K3S

Local Cluster

OS

Installing Rancher v2.5.4 on Hosted Kubernetes

Downstream Clusters in Rancher v2.5.4

Rancher RKE Downstream Clusters

Note: Rancher RKE Downstream clusters can be either provisioned by node drivers or custom/existing nodes, or registered into Rancher.

OS & Docker

Supported K8S Versions

Node Drivers

Rancher RKE Downstream Clusters (with Windows Worker Nodes)

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.

Supported Windows Server, Docker, K8S Versions

Refer these external links for more info related to Windows and Kubernetes:
Windows OS version support in Kubernetes
Windows Server release information

Rancher K3S Downstream Clusters

Note: Rancher K3S clusters can only be registered into Rancher.

OS

Supported K3S Versions

Rancher RKE2 Downstream Clusters

Note: Rancher RKE2, also known as RKE Government, clusters can only be registered into Rancher.

OS

Supported RKE2 Versions

Hosted Kubernetes Downstream Clusters

Note: Hosted Kubernetes clusters can be either provisioned by Rancher or registered into Rancher.

Supported K8S Versions

Other Registered Kubernetes Downstream Clusters

Note: Any Upstream Kubernetes conformant cluster can be registered.

Supported K8S Versions

Rancher Apps

Rancher Longhorn

Rancher Continuous Delivery

^† 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.

⁰ 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.

⁰⁰ 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

¹ 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

² 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.

³ whilst running kubernetes clusters in uncertified configurations may be possible, it is not recommended

⁴ upgrade of any individual component to a different version is likely to result in system downtime

⁵ 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.

⁶ SLA on node drivers is limited to those that are built-in and active by default when Rancher is installed

⁷ SLA does not apply to issues within an application and its lifecycle management

⁸ 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.