OS & Docker
CentOS |
7.7, 7.8, 7.9 |
Docker 17.03.2, 18.06.2, 18.09.x, 19.03.x |
|---|---|---|
Oracle Linux |
7.7, 7.9 |
Docker 19.03.x |
RancherOS |
1.5.6 |
Docker 17.03.2, 18.06.2, 18.09.x (up to 18.09.8), 19.03.x |
RHEL |
7.7, 7.8, 7.9 |
RHEL Docker 1.13.x |
SLES |
SLES 12 SP5, SLES 15 SP2 |
Docker 19.03.x |
Ubuntu |
16.04, 18.04, 20.04 |
Docker 17.03.2, 18.06.2, 18.09.x, 19.03.x |
Windows Server |
1809, 1903, 1909 |
Docker 19.03.x EE For worker nodes only 1909 is only applicable to downstream clusters running K8s 1.18 or later |
TYPE |
VERSION |
VALIDATED/CERTIFIED ON1 |
Rancher Kubernetes
Rancher Launched |
1.18.20 |
etcd: v3.4.3 |
|---|---|---|
Rancher Launched |
1.17.17 |
etcd: v3.4.3 |
Rancher Launched |
1.16.15 |
etcd: v3.3.15 |
Rancher Launched |
1.15.12 |
etcd: v3.3.10 |
TYPE |
UPSTREAM VERSION |
VALIDATED/CERTIFIED ON2 3 4 5 |
Hosted Kubernetes
AKS |
Microsoft Azure |
v1.18.8 |
|---|---|---|
EKS |
Amazon |
v1.18.8 |
GKE |
1.17.12 |
|
SERVICE |
PROVIDER |
VALIDATED/CERTIFIED ON‡ |
Imported Kubernetes
Existing |
v1.18.3+ v1.17.3+ v1.16.7+ v1.15.10+ |
Default settings of individual components |
|---|---|---|
K3s |
v1.18.16+k3s1 and newer v1.17.17+k3s1 and newer v1.16.14+ |
Architectures:
OS:
External Datastore Backend:
Components:
|
K3s |
v1.19.3+k3s3 and newer |
Architectures:
OS:
External Datastore Backend:
Components:
|
TYPE |
UPSTREAM VERSION |
VALIDATED/CERTIFIED ON2 3 4 5 |
Node Drivers
AWS |
Built-in, Active6 |
|
|---|---|---|
Azure |
Built-in, Active6 |
|
Digital Ocean |
Built-in, Active6 |
|
Linode |
Built-in, Active6 |
|
vSphere |
vSphere 6.5, 6.7, 7 |
Built-in, Active6 |
TYPE |
VERSION |
SLA LIMITED TO |
Monitoring
Prometheus and Grafana |
v0.1.5 |
0.1.5 prometheus: 2.18.2 prometheus-auth: v0.2.1 |
|---|---|---|
TYPE |
VERSION |
VALIDATED/CERTIFIED ON2 3 4 5 |
Istio
Istio |
v1.5.901 |
istio-citadel: v1.5.9 istio-galley: v1.5.9 istio-proxyv2: v1.5.9 istio-pilot: v1.5.9 istio-mixer: v1.5.9 istio-sidecar_injector: v1.5.9 jaegertracing-all-in-one: v1.14 kiali-kiali: v1.17 istio-node-agent-k8s: v1.5.9 coredns-coredns: v1.6.9 prom-prometheus: v2.18.2 jetstack-cert-manager-controller: v0.8.1 |
|---|---|---|
TYPE |
VERSION |
VALIDATED/CERTIFIED ON2 3 4 5 |
Catalog
Library |
None |
To the extent of being able to launch app with default configurations7 |
|---|---|---|
Partner |
To the extent of being able to launch app with default configurations7 8 |
|
Experimental |
N/A |
|
TYPE |
TAG |
SLA APPLIES |
† All “latest” tagged releases are intended for the Rancher community users to test-drive a new release and provide feedback. These “latest” tagged releases are not covered by Rancher SLA and not meant for production use cases either. Kindly use only the “stable” tagged releases to file support tickets and 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