Added ClusterRoleBinding for configmap.

.project

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>kubernetes-initializer-tutorial</name>
+	<comment></comment>
+	<projects>
+	</projects>
+	<buildSpec>
+	</buildSpec>
+	<natures>
+	</natures>
+</projectDescription>

docs/cleanup.md

@@ -10,6 +10,10 @@ kubectl delete initializerconfiguration envoy
 kubectl delete deployment envoy-initializer helloworld helloworld-with-annotation
 ```
 
+```
+kubectl delete clusterrolebindings cluster-admin-for-configmap
+```
+
 ```
 kubectl delete configmaps envoy envoy-initializer
 ```

docs/deploy-envoy-initializer.md

@@ -20,6 +20,14 @@ The Envoy Initializer is configured using a ConfigMap, identified by the `-confi
 kubectl apply -f configmaps/envoy-initializer.yaml
 ```
 
+### Create the ClusterRoleBinding
+
+The `ClusterRoleBinding` is needed to make sure the user `system:serviceaccount:default:default` have permission to get data from configmap `envoy-initializer`. 
+
+```
+kubectl apply -f rbac/bindings.yaml
+```
+
 ### Create the Envoy Initializer Deployment
 
 Deploy the `envoy-initializer` controller:

rbac/bindings.yaml

@@ -0,0 +1,12 @@
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+  name: cluster-admin-for-configmap
+roleRef:
+  apiGroup: rbac.authorization.k8s.io
+  kind: ClusterRole
+  name: cluster-admin
+subjects:
+- apiGroup: rbac.authorization.k8s.io
+  kind: User
+  name: system:serviceaccount:default:default