zoom_in Click to enlarge

Rancher Kubernetes Engine (RKE)

▲ ▼

language

description Rancher Kubernetes Engine (RKE) Overview

Rancher Kubernetes Engine (RKE) is a CNCF-certified, distribution of Kubernetes that prioritizes simplicity and security by utilizing a custom node configuration and agentless design for streamlined cluster deployment across diverse infrastructures.

help Rancher Kubernetes Engine (RKE) FAQ

How does RKE1 install Kubernetes on its nodes?

RKE1 connects to configured Linux hosts over SSH and runs Kubernetes components inside Docker containers. The desired nodes, roles, networking, and service options are declared in a cluster YAML file.

Does RKE require an agent to be installed on every node?

RKE1 uses an agentless provisioning model from the administrator's perspective, relying on SSH and Docker rather than a permanent RKE installer agent. Kubernetes services themselves still run as containers on each node according to its control-plane, etcd, or worker role.

Can RKE1 run on both bare-metal servers and virtual machines?

Yes, RKE1 is designed to work across bare-metal and virtualized infrastructure as long as the hosts meet its operating-system, SSH, and Docker requirements. This portability was a major reason teams used it for on-premises and cloud clusters.

Should a new Rancher cluster use RKE1 or RKE2?

A new deployment should generally use RKE2 because RKE1 has been deprecated and reached its announced end-of-life in 2025. RKE2 uses a different architecture, so an existing RKE1 cluster requires a planned workload and data migration rather than a simple in-place binary replacement.

swap_horiz

Looking for Rancher Kubernetes Engine (RKE) alternatives? Compare top competitors ranked & scored

arrow_forward