mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-10 19:25:48 +00:00
rm RKE1 references: rm rke1-vs-rke2-differences file
This commit is contained in:
Billy Tat
-37
@@ -1,37 +0,0 @@
|
||||
---
|
||||
title: Behavior Differences Between RKE1 and RKE2
|
||||
---
|
||||
|
||||
<head>
|
||||
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences"/>
|
||||
</head>
|
||||
|
||||
<EOLRKE1Warning />
|
||||
|
||||
RKE2, also known as RKE Government, is a Kubernetes distribution that focuses on security and compliance for U.S. Federal Government entities. It is considered the next iteration of the Rancher Kubernetes Engine, now known as RKE1.
|
||||
|
||||
RKE1 and RKE2 have several slight behavioral differences to note, and this page will highlight some of these at a high level.
|
||||
|
||||
### Control Plane Components
|
||||
|
||||
RKE1 uses Docker for deploying and managing control plane components, and it also uses Docker as the container runtime for Kubernetes. By contrast, RKE2 launches control plane components as static pods that are managed by the kubelet. RKE2's container runtime is containerd, which allows things such as mirroring a container image registry. RKE1 with Docker does not allow mirroring.
|
||||
|
||||
### Cluster API
|
||||
|
||||
RKE2/K3s provisioning is built on top of the Cluster API (CAPI) upstream framework which often makes RKE2-provisioned clusters behave differently than RKE1-provisioned clusters.
|
||||
|
||||
When you make changes to your cluster configuration in RKE2, this **may** result in nodes reprovisioning. This is controlled by CAPI controllers and not by Rancher itself. Note that for etcd nodes, the same behavior does not apply.
|
||||
|
||||
The following are some specific example configuration changes that may cause the described behavior:
|
||||
|
||||
- When editing the cluster and enabling `drain before delete`, the existing control plane nodes and worker are deleted and new nodes are created.
|
||||
|
||||
Users who are used to RKE1 provisioning should take note of this new RKE2 behavior which may be unexpected.
|
||||
|
||||
### Terminology
|
||||
|
||||
You will notice that some terms have changed or gone away going from RKE1 to RKE2. For example, in RKE1 provisioning, you use **node templates**; in RKE2 provisioning, you can configure your cluster node pools when creating or editing the cluster. Another example is that the term **node pool** in RKE1 is now known as **machine pool** in RKE2.
|
||||
|
||||
|
||||
|
||||
|
||||
-29
@@ -1,29 +0,0 @@
|
||||
---
|
||||
title: RKE1 和 RKE2 差异
|
||||
---
|
||||
|
||||
<EOLRKE1Warning />
|
||||
|
||||
RKE2，也称为 RKE Government，是一个完全符合标准的 Kubernetes 发行版，它专注于安全性和合规性。它被认为是 Rancher Kubernetes Engine（即 RKE1）的下一个迭代。
|
||||
|
||||
RKE1 和 RKE2 有一些细微的差异，本文将重点介绍这些差异。
|
||||
|
||||
## controlplane 组件
|
||||
|
||||
RKE1 使用 Docker 来部署和管理 controlplane 组件，还使用 Docker 作为 Kubernetes 的容器运行时。相比之下，RKE2 将 controlplane 组件作为由 kubelet 管理的静态 pod 启动。RKE2 的容器运行时是 Containerd，它允许 Mirror 容器镜像仓库等内容。使用 Docker 的 RKE1 不允许 Mirror。
|
||||
|
||||
## Cluster API
|
||||
|
||||
RKE2/K3s 配置是基于 Cluster API (CAPI) 上游框架之上构建的，这导致 RKE2 配置的集群的行为通常与 RKE1 配置的集群不同。
|
||||
|
||||
如果你在 RKE2 中更改集群配置，节点**可能**会重新配置。这是由 CAPI 控制器而不是 Rancher 控制的。请注意，etcd 节点不适用相同的行为。
|
||||
|
||||
以下是一些可能导致上述行为的配置更改示例：
|
||||
|
||||
- 编辑集群并启用`删除前清空`时，会删除现有的 controlplane 节点和 worker 并创建新节点。
|
||||
|
||||
如果你是习惯于 RKE1 配置的用户，请注意新的 RKE2 行为。
|
||||
|
||||
## 名词解释
|
||||
|
||||
从 RKE1 到 RKE2，某些术语已更改或已不再使用。例如，在 RKE1中，你使用**节点模板**，而在 RKE2 中，你可以在创建或编辑集群时配置集群节点池。另一个例子是 RKE1 中的**节点池（node pool）** 现在在 RKE2 中称为**主机池（machine pool）**。
|
||||
-29
@@ -1,29 +0,0 @@
|
||||
---
|
||||
title: RKE1 和 RKE2 差异
|
||||
---
|
||||
|
||||
<EOLRKE1Warning />
|
||||
|
||||
RKE2，也称为 RKE Government，是一个完全符合标准的 Kubernetes 发行版，它专注于安全性和合规性。它被认为是 Rancher Kubernetes Engine（即 RKE1）的下一个迭代。
|
||||
|
||||
RKE1 和 RKE2 有一些细微的差异，本文将重点介绍这些差异。
|
||||
|
||||
## controlplane 组件
|
||||
|
||||
RKE1 使用 Docker 来部署和管理 controlplane 组件，还使用 Docker 作为 Kubernetes 的容器运行时。相比之下，RKE2 将 controlplane 组件作为由 kubelet 管理的静态 pod 启动。RKE2 的容器运行时是 Containerd，它允许 Mirror 容器镜像仓库等内容。使用 Docker 的 RKE1 不允许 Mirror。
|
||||
|
||||
## Cluster API
|
||||
|
||||
RKE2/K3s 配置是基于 Cluster API (CAPI) 上游框架之上构建的，这导致 RKE2 配置的集群的行为通常与 RKE1 配置的集群不同。
|
||||
|
||||
如果你在 RKE2 中更改集群配置，节点**可能**会重新配置。这是由 CAPI 控制器而不是 Rancher 控制的。请注意，etcd 节点不适用相同的行为。
|
||||
|
||||
以下是一些可能导致上述行为的配置更改示例：
|
||||
|
||||
- 编辑集群并启用`删除前清空`时，会删除现有的 controlplane 节点和 worker 并创建新节点。
|
||||
|
||||
如果你是习惯于 RKE1 配置的用户，请注意新的 RKE2 行为。
|
||||
|
||||
## 名词解释
|
||||
|
||||
从 RKE1 到 RKE2，某些术语已更改或已不再使用。例如，在 RKE1中，你使用**节点模板**，而在 RKE2 中，你可以在创建或编辑集群时配置集群节点池。另一个例子是 RKE1 中的**节点池（node pool）** 现在在 RKE2 中称为**主机池（machine pool）**。
|
||||
@@ -558,8 +558,6 @@ const sidebars = {
|
||||
},
|
||||
],
|
||||
},
|
||||
"how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences",
|
||||
|
||||
"how-to-guides/new-user-guides/launch-kubernetes-with-rancher/about-rancher-agents",
|
||||
],
|
||||
},
|
||||
|
||||
-37
@@ -1,37 +0,0 @@
|
||||
---
|
||||
title: Behavior Differences Between RKE1 and RKE2
|
||||
---
|
||||
|
||||
<head>
|
||||
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences"/>
|
||||
</head>
|
||||
|
||||
<EOLRKE1Warning />
|
||||
|
||||
RKE2, also known as RKE Government, is a Kubernetes distribution that focuses on security and compliance for U.S. Federal Government entities. It is considered the next iteration of the Rancher Kubernetes Engine, now known as RKE1.
|
||||
|
||||
RKE1 and RKE2 have several slight behavioral differences to note, and this page will highlight some of these at a high level.
|
||||
|
||||
### Control Plane Components
|
||||
|
||||
RKE1 uses Docker for deploying and managing control plane components, and it also uses Docker as the container runtime for Kubernetes. By contrast, RKE2 launches control plane components as static pods that are managed by the kubelet. RKE2's container runtime is containerd, which allows things such as mirroring a container image registry. RKE1 with Docker does not allow mirroring.
|
||||
|
||||
### Cluster API
|
||||
|
||||
RKE2/K3s provisioning is built on top of the Cluster API (CAPI) upstream framework which often makes RKE2-provisioned clusters behave differently than RKE1-provisioned clusters.
|
||||
|
||||
When you make changes to your cluster configuration in RKE2, this **may** result in nodes reprovisioning. This is controlled by CAPI controllers and not by Rancher itself. Note that for etcd nodes, the same behavior does not apply.
|
||||
|
||||
The following are some specific example configuration changes that may cause the described behavior:
|
||||
|
||||
- When editing the cluster and enabling `drain before delete`, the existing control plane nodes and worker are deleted and new nodes are created.
|
||||
|
||||
Users who are used to RKE1 provisioning should take note of this new RKE2 behavior which may be unexpected.
|
||||
|
||||
### Terminology
|
||||
|
||||
You will notice that some terms have changed or gone away going from RKE1 to RKE2. For example, in RKE1 provisioning, you use **node templates**; in RKE2 provisioning, you can configure your cluster node pools when creating or editing the cluster. Another example is that the term **node pool** in RKE1 is now known as **machine pool** in RKE2.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -530,7 +530,6 @@
|
||||
}
|
||||
]
|
||||
},
|
||||
"how-to-guides/new-user-guides/launch-kubernetes-with-rancher/rke1-vs-rke2-differences",
|
||||
"how-to-guides/new-user-guides/launch-kubernetes-with-rancher/about-rancher-agents"
|
||||
]
|
||||
},
|
||||
|
||||
Reference in New Issue
Block a user