From 6953ddb8e615034381bf8ca26fe28b4e1c60e921 Mon Sep 17 00:00:00 2001 From: "Eli James (Cedric Chin)" Date: Sat, 24 Feb 2018 21:31:22 +0800 Subject: [PATCH] Update RBAC documentation for `endpoints` (#2139) For the Role named `nginx-ingress-role`, `endpoints` no longer needs or has `create` and `update` permissions. This confused me, so I hope this helps! --- deploy/rbac.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy/rbac.md b/deploy/rbac.md index 718269f36..ebf79aec2 100644 --- a/deploy/rbac.md +++ b/deploy/rbac.md @@ -43,7 +43,7 @@ These permissions are granted specific to the nginx-ingress namespace. These permissions are granted to the Role named `nginx-ingress-role` * `configmaps`, `pods`, `secrets`: get -* `endpoints`: create, get, update +* `endpoints`: get Furthermore to support leader-election, the nginx-ingress-controller needs to have access to a `configmap` using the resourceName `ingress-controller-leader-nginx`