From 86c0e4e5b9bb933c8f9c923b42549152b8973563 Mon Sep 17 00:00:00 2001 From: Gerald Mayr Date: Fri, 29 Apr 2022 20:27:22 +0200 Subject: [PATCH] Add missing verb --- .../migrating-telemetry-and-security-agents.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md index 13219bfd6d..3835057c91 100644 --- a/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md +++ b/content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents.md @@ -13,7 +13,7 @@ Kubernetes' support for direct integration with Docker Engine is deprecated, and ## Telemetry and security agents Within a Kubernetes cluster there are a few different ways to run telemetry or security agents. -Some agents have a direct dependency on Docker Engine when they as DaemonSets or +Some agents have a direct dependency on Docker Engine when they run as DaemonSets or directly on nodes. ### Why do some telemetry agents communicate with Docker Engine?