Overview

Rancher Labs Support Services are only for licensed users of a Rancher Labs products. Support for Rancher Labs products is offered at Standard and Platinum tiers. Company purchases support through the Rancher Labs sales department. The sales representative will provision the Company in the Rancher Labs Support Portal system, which will enable them to obtain Technical Support at the appropriate level of service.

Service Level Agreement (SLA)

The Rancher Labs SLA is defined in terms of initial response time after a Company has filed a case. Rancher Labs has defined 4 severity levels and their response time per plan for cases that are included in the table below. Company provides an initial severity level associated with a case. The Rancher Labs Support Manager will determine if the case was correctly classified and may increase or decrease the severity.

Level Description Standard Plan Response Time Platinum Plan Response Time
Severity 1 Severity 1 is defined as an incident where there is widespread failure or complete unavailability of Rancher functionality. A Severity 1 issue with an identified workaround will be reclassified as a Severity 2 issue. 4 hours 0900 – 1700 US Pacific Time Monday – Friday 1 hour 24 x 7 Every Day
Severity 2 Severity 2 is defined as an incident where core Rancher functionalities can continue to operate in a restricted fashion, although long-term productivity may be impacted. A Severity 2 issue with an identified workaround will be reclassified as a Severity 3 issue. 24 hours 0900 – 1700 US Pacific Time Monday – Friday 2 hours 0900 – 1700 US Pacific Time Monday – Friday
Severity 3 Severity 3 is defined as an incident that causes partial, non-critical loss of Rancher functionality. It may also be a major software defect that impacts Company when performing some actions and has no workaround. 2 business days 1 business day
Severity 4 Severity 4 is defined as: (1) request for Rancher Labs information or query, (2) feature requests for the product, (3) performance problems with little or no functionality impact, or (4) software defects with workarounds or medium or low functionality impact. No SLA No SLA

Rancher Support Lifecycle & Support Matrix

Products covered by SLAs are those validated and certified per the published support lifecycle and support matrix.

Important Definitions

"Major Releases" (X.y.z) are vehicles for delivering major features and enhancements. They are not guaranteed backwards compatibility with any previous major releases.

"Minor Releases" (x.Y.z) are vehicles for delivering minor feature developments, enhancements to existing features, and bug fixes. They incorporate all applicable fixes made in prior minor and maintenance releases.

"Maintenance Releases" (x.y.Z) are vehicles for delivering 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.

"Stable Releases" are releases that Rancher has promoted and recommends deploying in production setups.

Rancher Support Lifecycle

All major and minor Rancher versions enter the “Full Support” period immediately after they are released. These releases will receive enhancements to released features, security updates and bug fixes.

At the end of the "Full Support" period, versions enter the “Limited Support” period, during which only security updates will be provided. No enhancements to released features or bug fixes will be addressed during this time. The Rancher support team will still provide assistance and workarounds during this time.

At the end of the “Limited Support” period, versions enter the “End of Life (EOL)” period where they are no longer support eligible for any security updates,enhancements to released features, or bug fixes. Customers in the process of upgrading to an active Rancher version may contact our support team for assistance.

Rancher Version Start of Full Support Start of Limited Support End of Life
2.1.X Oct 19, 2018 Oct 19, 2019 April 19, 2020
2.0.X May 1, 2018 May 1, 2019 Nov 1, 2019
1.6.X June 8, 2017 Dec 31, 2019 June 30, 2020

Support Matrix

The following is the matrix of supported versions of Rancher as well as the corresponding components of Rancher, Kubernetes and Docker.

Versions 2.1.X
OS & Docker

Ubuntu 16.04

  • Docker 17.03.2

RancherOS v1.4.0

  • Docker 17.03.2

RHEL/CentOS 7.5

  • RHEL Docker 1.13
  • Docker 17.03.2
Rancher Kubernetes

v1.11.5

  • etcd: v3.2.18
  • flannel: v0.10.0
  • canal: v3.1.3
  • nginx-ingress-controller: 0.16.2

v1.10.11

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2

v1.9.7

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2
Hosted Kubernetes

GKE

  • up to v1.11.3

AKS

  • v1.11.5

EKS

  • v1.10.11
Imported Kubernetes
  • v1.11.5+
  • v1.10.11+
  • v1.9.7+
Node Drivers
  • Digital Ocean
  • AWS
  • Azure
  • vSphere - ESXi 6.5
OS & Docker

Ubuntu 16.04

  • Docker 17.03.2

RancherOS v1.4.0

  • Docker 17.03.2

RHEL/CentOS 7.5

  • RHEL Docker 1.13
  • Docker 17.03.2
Rancher Kubernetes

v1.11.3

  • etcd: v3.2.18
  • flannel: v0.10.0
  • canal: v3.1.3
  • nginx-ingress-controller: 0.16.2

v1.10.5

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2

v1.9.7

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2
Hosted Kubernetes

GKE

  • up to v1.10.7

AKS

  • v1.11.2

EKS

  • v1.10
Imported Kubernetes
  • v1.11.3+
  • v1.10.5+
  • v1.9.7+
Node Drivers
  • Digital Ocean
  • AWS
  • Azure
  • vSphere - ESXi 6.5
Versions 2.0.X
OS & Docker

Ubuntu 16.04

  • Docker 17.03.2

RancherOS v1.4.0

  • Docker 17.03.2

RHEL/CentOS 7.5

  • RHEL Docker 1.13
  • Docker 17.03.2
Rancher Kubernetes

v1.11.5

  • etcd: v3.2.18
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2

v1.10.11

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2

v1.9.7

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2
Hosted Kubernetes

GKE

  • up to v1.11.3

AKS

  • v1.11.5

EKS

  • v1.10.11
Imported Kubernetes
  • v1.11.5+
  • v1.10.11+
  • v1.9.7+
Node Drivers
  • Digital Ocean
  • AWS
  • Azure
  • vSphere - ESXi 6.5
OS & Docker

Ubuntu 16.04

  • Docker 17.03.2

RancherOS v1.4.0

  • Docker 17.03.2

RHEL/CentOS 7.5

  • RHEL Docker 1.13
  • Docker 17.03.2
Rancher Kubernetes

v1.11.2

  • etcd: v3.2.18
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2

v1.10.5

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2

v1.9.7

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.16.2
Hosted Kubernetes

GKE

  • up to v1.10.7

AKS

  • v1.8.11

EKS

  • v1.10
Imported Kubernetes
  • v1.11.2+
  • v1.10.5+
  • v1.9.7+
Node Drivers
  • Digital Ocean
  • AWS
  • Azure
  • vSphere - ESXi 6.5
OS & Docker

Ubuntu 16.04

  • Docker 17.03.2

RancherOS v1.4.0

  • Docker 17.03.2

RHEL/CentOS 7.5

  • RHEL Docker 1.13
  • Docker 17.03.2
Rancher Kubernetes

v1.10.5

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2

v1.9.7

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2

v1.8.11

  • etcd: v3.0.17
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2
Hosted Kubernetes

GKE

  • up to v1.10.7

AKS

  • v1.8.11

EKS

  • v1.10
Imported Kubernetes
  • v1.10.5+
  • v1.9.7+
  • v1.8.11+
Node Drivers
  • Digital Ocean
  • AWS
  • Azure
  • vSphere - ESXi 6.5
OS & Docker

Ubuntu 16.04

  • Docker 17.03.2

RancherOS v1.4.0

  • Docker 17.03.2

RHEL/CentOS 7.5

  • RHEL Docker 1.13
  • Docker 17.03.2
Rancher Kubernetes

v1.10.3

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2

v1.9.7

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2

v1.8.11

  • etcd: v3.0.17
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2
Hosted Kubernetes

GKE

  • up to v1.10.7

AKS

  • v1.8.11

EKS

  • v1.10
Imported Kubernetes
  • v1.10.3+
  • v1.9.7+
  • v1.8.11+
Node Drivers
  • Digital Ocean
  • AWS
  • Azure
  • vSphere - ESXi 6.5
OS & Docker

Ubuntu 16.04

  • Docker 17.03.2

RancherOS v1.3.0

  • Docker 17.03.2

RHEL/CentOS 7.5

  • RHEL Docker 1.13
  • Docker 17.03.2
Rancher Kubernetes

v1.10.1

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2

v1.9.7

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2

v1.8.11

  • etcd: v3.0.17
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2
Hosted Kubernetes

GKE

  • up to v1.10.7

AKS

  • v1.8.1

EKS

  • Not supported
Imported Kubernetes
  • v1.10.1+
  • v1.9.7+
  • v1.8.11+
Node Drivers
  • Digital Ocean
  • AWS
  • Azure
  • vSphere - ESXi 6.5
OS & Docker

Ubuntu 16.04

  • Docker 17.03.2

RancherOS v1.3.0

  • Docker 17.03.2

RHEL/CentOS 7.5

  • RHEL Docker 1.13
  • Docker 17.03.2
Rancher Kubernetes

v1.10.1

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2

v1.9.7

  • etcd: v3.1.12
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2

v1.8.11

  • etcd: v3.0.17
  • flannel: v0.9.1
  • canal: v3.1.1
  • nginx-ingress-controller: 0.10.2
Hosted Kubernetes

GKE

  • up to v1.10.7

AKS

  • v1.8.1

EKS

  • Not supported
Imported Kubernetes
  • v1.10.1+
  • v1.9.7+
  • v1.8.11+
Node Drivers
  • Digital Ocean
  • AWS
  • Azure
  • vSphere - ESXi 6.5
Versions 1.6.X
OS & Docker

RHEL/CentOS: 7.5

  • RHEL Docker: 1.13

Ubuntu: 14.04, 16.04, 18.04

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03, 18.06
  • Docker for Kubernetes: 17.03

RancherOS: v1.4.2

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03
  • Docker for Kubernetes: 17.03
Rancher Components

Agent Image

  • rancher/agent:v1.2.11

Load Balancer Image

  • rancher/lb-service-haproxy:v0.9.6

Rancher CLI

  • v0.6.12
Infrastructure Stacks

Network Services Template - v0.2.10

  • rancher/network-manager:v0.7.22
  • rancher/metadata:v0.10.4
  • rancher/dns:v0.17.4

Ipsec Template - 0.2.5

  • rancher/net:v0.13.17

Healthcheck Template - v0.3.8

  • rancher/healthcheck:v0.3.8

Scheduler Template - v0.8.5

  • rancher/scheduler:v0.8.5
Kubernetes Versions
  • v1.11.5
OS & Docker

RHEL/CentOS: 7.5

  • RHEL Docker: 1.13

Ubuntu: 14.04, 16.04, 18.04

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03, 18.06
  • Docker for Kubernetes: 17.03

RancherOS: v1.4.0

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03
  • Docker for Kubernetes: 17.03
Rancher Components

Agent Image

  • rancher/agent:v1.2.11

Load Balancer Image

  • rancher/lb-service-haproxy:v0.9.6

Rancher CLI

  • v0.6.12
Infrastructure Stacks

Network Services Template - v0.2.10

  • rancher/network-manager:v0.7.22
  • rancher/metadata:v0.10.4
  • rancher/dns:v0.17.4

Ipsec Template - 0.2.5

  • rancher/net:v0.13.17

Healthcheck Template - v0.3.8

  • rancher/healthcheck:v0.3.8

Scheduler Template - v0.8.5

  • rancher/scheduler:v0.8.5
Kubernetes Versions
  • v1.11.2
OS & Docker

RHEL/CentOS: 7.5

  • RHEL Docker: 1.13

Ubuntu: 14.04, 16.04, 18.04

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03, 18.06
  • Docker for Kubernetes: 17.03

RancherOS: v1.4.0

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03
  • Docker for Kubernetes: 17.03
Rancher Components

Agent Image

  • rancher/agent:v1.2.11

Load Balancer Image

  • rancher/lb-service-haproxy:v0.9.6

Rancher CLI

  • v0.6.12
Infrastructure Stacks

Network Services Template - v0.2.10

  • rancher/network-manager:v0.7.22
  • rancher/metadata:v0.10.4
  • rancher/dns:v0.17.4

Ipsec Template - 0.2.5

  • rancher/net:v0.13.17

Healthcheck Template - v0.3.8

  • rancher/healthcheck:v0.3.8

Scheduler Template - v0.8.5

  • rancher/scheduler:v0.8.5
Kubernetes Versions
  • v1.11.2
OS & Docker

RHEL/CentOS: 7.5

  • RHEL Docker: 1.13

Ubuntu: 14.04, 16.04, 18.04

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03, 18.06
  • Docker for Kubernetes: 17.03

RancherOS: v1.4.0

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03
  • Docker for Kubernetes: 17.03
Rancher Components

Agent Image

  • rancher/agent:v1.2.11

Load Balancer Image

  • rancher/lb-service-haproxy:v0.9.6

Rancher CLI

  • v0.6.12
Infrastructure Stacks

Network Services Template - v0.2.10

  • rancher/network-manager:v0.7.22
  • rancher/metadata:v0.10.4
  • rancher/dns:v0.17.4

Ipsec Template - 0.2.5

  • rancher/net:v0.13.17

Healthcheck Template - v0.3.8

  • rancher/healthcheck:v0.3.8

Scheduler Template - v0.8.5

  • rancher/scheduler:v0.8.5
Kubernetes Versions
  • v1.11.2
OS & Docker

RHEL/CentOS: 7.5

  • RHEL Docker: 1.13

Ubuntu: 14.04, 16.04, 18.04

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03, 18.06
  • Docker for Kubernetes: 17.03

RancherOS: v1.4.0

  • Docker for Cattle: 17.06, 17.09, 17.12, 18.03
  • Docker for Kubernetes: 17.03
Rancher Components

Agent Image

  • rancher/agent:v1.2.11

Load Balancer Image

  • rancher/lb-service-haproxy:v0.9.3

Rancher CLI

  • v0.6.11
Infrastructure Stacks

Network Services Template - v0.2.10

  • rancher/network-manager:v0.7.22
  • rancher/metadata:v0.10.4
  • rancher/dns:v0.17.4

Ipsec Template - 0.2.5

  • rancher/net:v0.13.1

Healthcheck Template - v0.3.8

  • rancher/healthcheck:v0.3.8

Scheduler Template - v0.8.5

  • rancher/scheduler:v0.8.5
Kubernetes Versions
  • v1.11.1
  • v1.10.5
OS & Docker

RHEL/CentOS: 7.4

  • RHEL Docker: 1.13

Ubuntu: 14.04, 16.04

  • Docker for Cattle: 17.03, 17.06, 17.09, 17.12, 18.03
  • Docker for Kubernetes: 17.03

RancherOS: v1.3.0

  • Docker for Cattle: 17.03, 17.06, 17.09, 17.12
  • Docker for Kubernetes: 17.03
Rancher Components

Agent Image

  • rancher/agent:v1.2.10

Load Balancer Image

  • rancher/lb-service-haproxy:v0.9.1

Rancher CLI

  • v0.6.10
Infrastructure Stacks

Network Services Template - v0.2.9

  • rancher/network-manager:v0.7.20
  • rancher/metadata:v0.10.2
  • rancher/dns:v0.17.3

Ipsec Template - 0.2.4

  • rancher/net:v0.13.13

Healthcheck Template - v0.3.6

  • rancher/healthcheck:v0.3.6

Scheduler Template - v0.8.3-1

  • rancher/scheduler:v0.8.3
Kubernetes Versions
  • v1.10.3
  • v1.9.5
  • v1.8.10
OS & Docker

RHEL/CentOS: 7.4

  • RHEL Docker: 1.13

Ubuntu: 14.04, 16.04

  • Docker for Cattle: 17.03, 17.06, 17.09, 17.12
  • Docker for Kubernetes: 17.03

RancherOS: v1.3.0

  • Docker for Cattle: 17.03, 17.06, 17.09, 17.12
  • Docker for Kubernetes: 17.03
Rancher Components

Agent Image

  • rancher/agent:v1.2.10

Load Balancer Image

  • rancher/lb-service-haproxy:v0.9.1

Rancher CLI

  • v0.6.9
Infrastructure Stacks

Network Services Template - v0.2.9

  • rancher/network-manager:v0.7.20
  • rancher/metadata:v0.10.2
  • rancher/dns:v0.17.3

Ipsec Template - 0.2.3

  • rancher/net:v0.13.11

Healthcheck Template - v0.3.6

  • rancher/healthcheck:v0.3.6

Scheduler Template - v0.8.3-1

  • rancher/scheduler:v0.8.3
Kubernetes Versions
  • v1.10.0
  • v1.9.5
  • v1.8.10
OS & Docker

RHEL/CentOS: 7.4

  • RHEL Docker: 1.13

Ubuntu: 14.04, 16.04

  • Docker for Cattle: 17.03, 17.06, 17.09, 17.12
  • Docker for Kubernetes: 17.03

RancherOS: v1.3.0

  • Docker for Cattle: 17.03, 17.06, 17.09, 17.12
  • Docker for Kubernetes: 17.03
Rancher Components

Agent Image

  • rancher/agent:v1.2.10

Load Balancer Image

  • rancher/lb-service-haproxy:v0.9.1

Rancher CLI

  • v0.6.8
Infrastructure Stacks

Network Services Template - v0.2.9

  • rancher/network-manager:v0.7.20
  • rancher/metadata:v0.10.2
  • rancher/dns:v0.17.3

Ipsec Template - 0.2.3

  • rancher/net:v0.13.11

Healthcheck Template - v0.3.6

  • rancher/healthcheck:v0.3.6

Scheduler Template - v0.8.3-1

  • rancher/scheduler:v0.8.3
Kubernetes Versions
  • v1.9.5
  • v1.8.10

Cases

A case 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 case exists in the Rancher Labs Support Portal and includes all the communication associated with the issue.


Support Portal Access and Case Entry

Rancher Labs provides a full featured, web-based case 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 case submission. The support portal allows Company to enter cases, add information to existing cases, receive information and updates about cases, close cases, and list their currently open and closed cases.


Customizations

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 support case.


Escalation Path

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 Sales to discuss issues that the support team has been unable to resolve for some time or that were resolved in an unsatisfactory manner.


Effect of Termination or Non-Renewal of Support Services

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


Reinstatement of Support Services

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


Access

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