From 18e5d14344bd4eaf75597fd06ada1be241a5a08a Mon Sep 17 00:00:00 2001
From: Tim Bannister <tim@scalefactory.com>
Date: Mon, 12 Oct 2020 21:52:33 +0100
Subject: [PATCH] Remove rkt

https://github.com/rkt/rkt is an ex-project.
rkt has kicked the bucket, shuffled off its mortal coil, run down the
curtain and joined the choir invisible.
---
 content/en/docs/reference/glossary/rkt.md      | 18 ------------------
 .../create-cluster/cluster-intro.html          |  2 +-
 2 files changed, 1 insertion(+), 19 deletions(-)
 delete mode 100644 content/en/docs/reference/glossary/rkt.md

diff --git a/content/en/docs/reference/glossary/rkt.md b/content/en/docs/reference/glossary/rkt.md
deleted file mode 100644
index 165bce5406..0000000000
--- a/content/en/docs/reference/glossary/rkt.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: rkt
-id: rkt
-date: 2019-01-24
-full_link: https://coreos.com/rkt/
-short_description: >
-  A security-minded, standards-based container engine.
-
-aka: 
-tags:
-- security
-- tool
----
- A security-minded, standards-based container engine.
-
-<!--more--> 
-
-rkt is an application {{< glossary_tooltip text="container" term_id="container" >}} engine featuring a {{< glossary_tooltip text="Pod" term_id="pod" >}}-native approach, a pluggable execution environment, and a well-defined surface area. rkt allows users to apply different configurations at both the Pod and application level. Each Pod executes directly in the classic Unix process model, in a self-contained, isolated environment.
diff --git a/content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html b/content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html
index 13d3d99758..5ac682d7af 100644
--- a/content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html
+++ b/content/en/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html
@@ -72,7 +72,7 @@ weight: 10
         <div class="row">
             <div class="col-md-8">
                 <p><b>The Master is responsible for managing the cluster.</b> The master coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.</p>
-                <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes master. The node should also have tools for handling container operations, such as Docker or rkt. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p>
+                <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes master. The node should also have tools for handling container operations, such as containerd or Docker. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p>
 
             </div>
             <div class="col-md-4">