Update requirements for Windows server OS

This commit is contained in:
Catherine Luse
2021-05-04 17:05:56 -07:00
parent d15d504c6a
commit d3f196c4e2
2 changed files with 11 additions and 1 deletions
@@ -33,6 +33,14 @@ The general node requirements for networking, operating systems, and Docker are
### OS and Docker Requirements
{{% tabs %}}
{{% tab "Rancher v2.5.8+" %}}
Our support for Windows servers matches the Microsoft official lifecycle for LTSC (Long-Term Servicing Channel) and SAC (Semi-Annual Channel) servers.
For the support end dates for each Windows server, see the [Microsoft Documentation.](https://docs.microsoft.com/en-us/windows-server/get-started/windows-server-release-info)
{{% /tab %}}
{{% tab "Rancher before v2.5.8" %}}
In order to add Windows worker nodes to a cluster, the node must be running one of the following Windows Server versions and the corresponding version of Docker Engine - Enterprise Edition (EE):
- Nodes with Windows Server core version 1809 should use Docker EE-basic 18.09 or Docker EE-basic 19.03.
@@ -42,6 +50,8 @@ In order to add Windows worker nodes to a cluster, the node must be running one
>
> - If you are using AWS, Rancher recommends _Microsoft Windows Server 2019 Base with Containers_ as the Amazon Machine Image (AMI).
> - If you are using GCE, Rancher recommends _Windows Server 2019 Datacenter for Containers_ as the OS image.
{{% /tab %}}
{{% /tabs %}}
### Kubernetes Version
+1 -1
View File
@@ -11,7 +11,7 @@ ctaBanner: 0
> We are transitioning to versioned documentation. The Rancher v2.5 docs are [here.]({{<baseurl>}}/rancher/v2.5/en/) The Rancher v2.0-v2.4 docs are [here.]({{<baseurl>}}/rancher/v2.0-v2.4/en/) We recommend using the versioned docs because they are easier to read and navigate.
>
> This section, formerly called 2.x, contains information for versions v2.0-2.5.6. This section is still on the Rancher website so that search results won't return 404 errors, but it will no longer be maintained.
> This section, also called 2.x, contains information for versions v2.0-2.5.6. This section is still on the Rancher website so that search results won't return 404 errors, but it will no longer be maintained.
Rancher was originally built to work with multiple orchestrators, and it included its own orchestrator called Cattle. With the rise of Kubernetes in the marketplace, Rancher 2.x exclusively deploys and manages Kubernetes clusters running anywhere, on any provider.