From 603f8109032469e6808e6c91501819b5f41c43b4 Mon Sep 17 00:00:00 2001 From: "David M. Lentz" Date: Tue, 23 Aug 2022 14:43:41 -0600 Subject: [PATCH] Fix typo There are redundant instances of "future" in this sentence. --- content/en/docs/concepts/security/rbac-good-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/security/rbac-good-practices.md b/content/en/docs/concepts/security/rbac-good-practices.md index 933dbdb9bb3..5c2e104c4e7 100644 --- a/content/en/docs/concepts/security/rbac-good-practices.md +++ b/content/en/docs/concepts/security/rbac-good-practices.md @@ -32,7 +32,7 @@ some general rules that can be applied are : ClusterRoleBindings to give users rights only within a specific namespace. - Avoid providing wildcard permissions when possible, especially to all resources. As Kubernetes is an extensible system, providing wildcard access gives rights - not just to all object types that currently exist in the cluster, but also to all future object types + not just to all object types that currently exist in the cluster, but also to all object types which are created in the future. - Administrators should not use `cluster-admin` accounts except where specifically needed. Providing a low privileged account with