Merge pull request #20185 from gauravsofat/fix-rbac-auth-msg

Modify RBAC Authorizer log message
2020-04-08 22:39:44 -07:00 · 2020-04-08 22:39:44 -07:00 · 2259c8c52f
parent 12b62a8317 09b1eb29d3
commit 2259c8c52f
1 changed files with 1 additions and 1 deletions
--- a/content/en/docs/reference/access-authn-authz/rbac.md
+++ b/content/en/docs/reference/access-authn-authz/rbac.md
@ -1182,7 +1182,7 @@ allowed by *either* the RBAC or ABAC policies is allowed.

 When the kube-apiserver is run with a log level of 5 or higher for the RBAC component
 (`--vmodule=rbac*=5` or `--v=5`), you can see RBAC denials in the API server log
-(prefixed with `RBAC DENY:`).
+(prefixed with `RBAC`).
 You can use that information to determine which roles need to be granted to which users, groups, or service accounts.

 Once you have [granted roles to service accounts](#service-account-permissions) and workloads