From 45a0819cdc0ec4696ff8bd28ce6562520c228a77 Mon Sep 17 00:00:00 2001
From: Eric Chiang <eric.chiang.m@gmail.com>
Date: Fri, 6 Apr 2018 12:12:08 -0700
Subject: [PATCH] rbac: make it clear that subjects are case sensitive (#8007)

---
 docs/admin/authorization/rbac.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/admin/authorization/rbac.md b/docs/admin/authorization/rbac.md
index 274e23522b..34b0950d97 100644
--- a/docs/admin/authorization/rbac.md
+++ b/docs/admin/authorization/rbac.md
@@ -88,7 +88,7 @@ metadata:
   namespace: default
 subjects:
 - kind: User
-  name: jane
+  name: jane # Name is case sensitive
   apiGroup: rbac.authorization.k8s.io
 roleRef:
   kind: Role
@@ -102,7 +102,7 @@ This allows administrators to define a set of common roles for the entire cluste
 then reuse them within multiple namespaces.
 
 For instance, even though the following `RoleBinding` refers to a `ClusterRole`,
-"dave" (the subject) will only be able to read secrets in the "development"
+"dave" (the subject, case sensitive) will only be able to read secrets in the "development"
 namespace (the namespace of the `RoleBinding`).
 
 ```yaml
@@ -114,7 +114,7 @@ metadata:
   namespace: development # This only grants permissions within the "development" namespace.
 subjects:
 - kind: User
-  name: dave
+  name: dave # Name is case sensitive
   apiGroup: rbac.authorization.k8s.io
 roleRef:
   kind: ClusterRole
@@ -134,7 +134,7 @@ metadata:
   name: read-secrets-global
 subjects:
 - kind: Group
-  name: manager
+  name: manager # Name is case sensitive
   apiGroup: rbac.authorization.k8s.io
 roleRef:
   kind: ClusterRole