Fixes namespac in clusterrolebinding in getting-started

docs/getting-started/README.md

@@ -55,7 +55,8 @@ Configure your cluster as follows:
 2. Create the [`admin` user, role, and rolebinding](./rbac/admin-role.yaml) using the following command:
 
    ```
-   kubectl -n getting-started apply -f ./docs/getting-started/rbac/admin-role.yaml
+   kubectl -n getting-started apply -f ./docs/getting-started/rbac/admin-role.yaml \
+               -f ./docs/getting-started/rbac/clusterrolebinding.yaml
    ```
 3. (Optional) If you have already provisioned a cluster secret for a "Let's Encrypt" certificate,
    you must export it and then import it into your `getting-started` namespace. For example:

docs/getting-started/rbac/clusterrolebinding.yaml

@@ -0,0 +1,12 @@
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+  name: tekton-triggers-getting-started-clusterbinding
+subjects:
+- kind: ServiceAccount
+  name: tekton-triggers-example-sa
+  namespace: getting-started
+roleRef:
+  apiGroup: rbac.authorization.k8s.io
+  kind: ClusterRole
+  name: tekton-triggers-example-clusterrole

docs/getting-started/rbac/webhook-role.yaml

@@ -49,6 +49,7 @@ metadata:
 subjects:
   - kind: ServiceAccount
     name: tekton-triggers-createwebhook
+    namespace: getting-started
 roleRef:
   apiGroup: rbac.authorization.k8s.io
   kind: Role