From 4a62e21cad17ed4216faeba9a5684ad5c9d7537a Mon Sep 17 00:00:00 2001 From: Martin Mosegaard Amdisen Date: Mon, 12 Feb 2018 20:25:49 +0100 Subject: [PATCH] Update securing-a-cluster.md (#7367) Remove extra word. --- docs/tasks/administer-cluster/securing-a-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/administer-cluster/securing-a-cluster.md b/docs/tasks/administer-cluster/securing-a-cluster.md index befd59315b..f6b405d4c3 100644 --- a/docs/tasks/administer-cluster/securing-a-cluster.md +++ b/docs/tasks/administer-cluster/securing-a-cluster.md @@ -39,7 +39,7 @@ potentially unsecured traffic. Choose an authentication mechanism for the API servers to use that matches the common access patterns when you install a cluster. For instance, small single user clusters may wish to use a simple certificate -or static Bearer token approach. Larger clusters may wish to integrate an existing or OIDC or LDAP server that +or static Bearer token approach. Larger clusters may wish to integrate an existing OIDC or LDAP server that allow users to be subdivided into groups. All API clients must be authenticated, even those that are part of the infrastructure like nodes,