mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-05-16 18:13:17 +00:00
Merge pull request #3826 from jtravee/rancherd-deprecation
Updated/added RancherD notes to reflect discontinuation
This commit is contained in:
Jen Travinski
GitHub
@@ -17,7 +17,7 @@ In this section,
|
||||
- **RKE (Rancher Kubernetes Engine)** is a certified Kubernetes distribution and CLI/library which creates and manages a Kubernetes cluster.
|
||||
- **K3s (Lightweight Kubernetes)** is also a fully compliant Kubernetes distribution. It is newer than RKE, easier to use, and more lightweight, with a binary size of less than 100 MB.
|
||||
- **RKE2** is a fully conformant Kubernetes distribution that focuses on security and compliance within the U.S. Federal Government sector.
|
||||
- **RancherD** is a new tool for installing Rancher, which is available as of Rancher v2.5.4. It is an experimental feature. RancherD is a single binary that first launches an RKE2 Kubernetes cluster, then installs the Rancher server Helm chart on the cluster.
|
||||
- **RancherD** was an experimental tool for installing Rancher; a single binary that first launched an RKE2 Kubernetes cluster, then installed the Rancher server Helm chart on the cluster. It was available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
# Changes to Installation in Rancher v2.5
|
||||
|
||||
@@ -37,9 +37,7 @@ We recommend using Helm, a Kubernetes package manager, to install Rancher on mul
|
||||
|
||||
### High-availability Kubernetes Install with RancherD
|
||||
|
||||
_Available as of v2.5.4_
|
||||
|
||||
> This is an experimental feature.
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
RancherD is a single binary that first launches an RKE2 Kubernetes cluster, then installs the Rancher server Helm chart on the cluster.
|
||||
|
||||
|
||||
+1
-3
@@ -6,9 +6,7 @@ aliases:
|
||||
- /rancher/v2.x/en/installation/install-rancher-on-linux/
|
||||
---
|
||||
|
||||
_Available as of Rancher v2.5.4_
|
||||
|
||||
> This is an experimental feature.
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
We are excited to introduce a new, simpler way to install Rancher called RancherD.
|
||||
|
||||
|
||||
+1
-1
@@ -6,7 +6,7 @@ aliases:
|
||||
- /rancher/v2.x/en/installation/install-rancher-on-linux/rancherd-configuration/
|
||||
---
|
||||
|
||||
> RancherD is an experimental feature.
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
In RancherD, a server node is defined as a machine (bare-metal or virtual) running the `rancherd server` command. The server runs the Kubernetes API as well as Kubernetes workloads.
|
||||
|
||||
|
||||
+1
-1
@@ -6,6 +6,6 @@ aliases:
|
||||
- /rancher/v2.x/en/installation/install-rancher-on-linux/rollbacks/
|
||||
---
|
||||
|
||||
> RancherD is an experimental feature.
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
To roll back Rancher to a previous version, re-run the installation script with the previous version specified in the `INSTALL_RANCHERD_VERSION` environment variable.
|
||||
+1
-1
@@ -6,7 +6,7 @@ aliases:
|
||||
- /rancher/v2.x/en/installation/install-rancher-on-linux/upgrades/
|
||||
---
|
||||
|
||||
> RancherD is an experimental feature.
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
When RancherD is upgraded, the Rancher Helm controller and the Fleet pods are upgraded.
|
||||
|
||||
|
||||
@@ -80,7 +80,7 @@ If you are installing Rancher on a K3s cluster with Alpine Linux, follow [these
|
||||
|
||||
### RancherD Specific Requirements
|
||||
|
||||
_The RancherD install is available as of v2.5.4. It is an experimental feature._
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
At this time, only Linux OSes that leverage systemd are supported.
|
||||
|
||||
@@ -103,6 +103,7 @@ The Ingress should be deployed as DaemonSet to ensure your load balancer can suc
|
||||
Docker is required for Helm chart installs, and it can be installed by following the steps in the official [Docker documentation.](https://docs.docker.com/) Rancher also provides [scripts]({{<baseurl>}}/rancher/v2.5/en/installation/requirements/installing-docker) to install Docker with one command.
|
||||
|
||||
Docker is not required for RancherD installs.
|
||||
|
||||
# Hardware Requirements
|
||||
|
||||
The following sections describe the CPU, memory, and disk requirements for the nodes where the Rancher server is installed.
|
||||
@@ -143,7 +144,7 @@ These CPU and memory requirements apply to each host in a [K3s Kubernetes cluste
|
||||
|
||||
### RancherD
|
||||
|
||||
_RancherD is available as of v2.5.4. It is an experimental feature._
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
These CPU and memory requirements apply to each instance with RancherD installed. Minimum recommendations are outlined here.
|
||||
|
||||
|
||||
@@ -119,6 +119,8 @@ The following tables break down the port requirements for inbound and outbound t
|
||||
|
||||
### Ports for Rancher Server Nodes on RancherD or RKE2
|
||||
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
{{% accordion label="Click to expand" %}}
|
||||
|
||||
The RancherD (or RKE2) server needs port 6443 and 9345 to be accessible by other nodes in the cluster.
|
||||
|
||||
@@ -14,6 +14,8 @@ For Docker installations of Rancher, which is used for development and testing,
|
||||
|
||||
The Helm chart version also applies to RancherD installs because RancherD installs the Rancher Helm chart on a Kubernetes cluster.
|
||||
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
{{% tabs %}}
|
||||
{{% tab "Helm Charts" %}}
|
||||
|
||||
|
||||
@@ -7,6 +7,8 @@ aliases:
|
||||
|
||||
Docker is required to be installed on nodes where the Rancher server will be installed with Helm or Docker. Docker is not required for RancherD installs.
|
||||
|
||||
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
|
||||
|
||||
There are a couple of options for installing Docker. One option is to refer to the [official Docker documentation](https://docs.docker.com/install/) about how to install Docker on Linux. The steps will vary based on the Linux distribution.
|
||||
|
||||
Another option is to use one of Rancher's Docker installation scripts, which are available for most recent versions of Docker.
|
||||
|
||||
Reference in New Issue
Block a user