From c7e57cb67cde0349063d34872aba6766a14d56a6 Mon Sep 17 00:00:00 2001 From: Derek Date: Mon, 5 Aug 2019 17:39:49 -0500 Subject: [PATCH] TLS is Transport Layer Security; not level (#14998) See https://en.wikipedia.org/wiki/Transport_Layer_Security --- content/en/docs/tasks/administer-cluster/securing-a-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/securing-a-cluster.md b/content/en/docs/tasks/administer-cluster/securing-a-cluster.md index 36de25de82..e588ecc369 100644 --- a/content/en/docs/tasks/administer-cluster/securing-a-cluster.md +++ b/content/en/docs/tasks/administer-cluster/securing-a-cluster.md @@ -28,7 +28,7 @@ and provides recommendations on overall security. As Kubernetes is entirely API driven, controlling and limiting who can access the cluster and what actions they are allowed to perform is the first line of defense. -### Use Transport Level Security (TLS) for all API traffic +### Use Transport Layer Security (TLS) for all API traffic Kubernetes expects that all API communication in the cluster is encrypted by default with TLS, and the majority of installation methods will allow the necessary certificates to be created and distributed to