Update RBAC configuration and docs to include leases resource for leader election

docs/haproxy-ingress.yaml

@@ -71,6 +71,14 @@ metadata:
   name: ingress-controller
   namespace: ingress-controller
 rules:
+  - apiGroups:
+      - coordination.k8s.io
+    resources:
+      - leases
+    verbs:
+      - get
+      - create
+      - update
   - apiGroups:
       - ""
     resources:

docs/static/resources/haproxy-ingress.yaml

@@ -40,9 +40,10 @@ rules:
       - list
       - watch
   - apiGroups:
-      - "extensions"
-      - "networking.k8s.io"
+      - extensions
+      - networking.k8s.io
     resources:
+      - ingressclasses
       - ingresses
     verbs:
       - get
@@ -56,8 +57,8 @@ rules:
       - create
       - patch
   - apiGroups:
-      - "extensions"
-      - "networking.k8s.io"
+      - extensions
+      - networking.k8s.io
     resources:
       - ingresses/status
     verbs:
@@ -69,6 +70,14 @@ metadata:
   name: ingress-controller
   namespace: ingress-controller
 rules:
+  - apiGroups:
+      - coordination.k8s.io
+    resources:
+      - leases
+    verbs:
+      - get
+      - create
+      - update
   - apiGroups:
       - ""
     resources:

examples/rbac/README.md

@@ -41,9 +41,11 @@ The Role permissions are:
 * `endpoints`: create, get, update
 
 Furthermore to support leader-election, the ingress controller needs to
-have access to a `configmap` in the `ingress-controller` namespace:
+have access to both the `configmap` and `leases` resources in the
+`ingress-controller` namespace:
 
 * `configmaps`: get, update, create
+* `coordination.k8s.io/leases`: get, update, create
 
 ## Namespace created in this example
 

examples/rbac/ingress-controller-rbac.yml

@@ -71,6 +71,14 @@ metadata:
   name: ingress-controller
   namespace: ingress-controller
 rules:
+  - apiGroups:
+      - coordination.k8s.io
+    resources:
+      - leases
+    verbs:
+      - get
+      - create
+      - update
   - apiGroups:
       - ""
     resources: