diff --git a/config/manager/role.yaml b/config/manager/role.yaml
index 675adf7..031d7d0 100644
--- a/config/manager/role.yaml
+++ b/config/manager/role.yaml
@@ -5,7 +5,9 @@ metadata:
   creationTimestamp: null
   name: kube-trigger-manager-role
 rules:
-- resources:
+- apiGroups:
+  - ""
+  resources:
   - configmaps
   verbs:
   - get
diff --git a/examples/README.md b/examples/README.md
index a6e9eb0..35be2d1 100644
--- a/examples/README.md
+++ b/examples/README.md
@@ -7,6 +7,10 @@ updated whenever the ConfigMaps that are referenced by `ref-objects` are updated
 ## Prerequisites
 
 - Install [KubeVela](https://kubevela.net/docs/install) in your cluster
+- Enable the `kube-trigger` addon
+```shell
+vela addon enable kube-trigger
+```
 
 ## What we want to achieve?
 
@@ -26,7 +30,7 @@ Apply `sample.yaml` to create 2 Applications and 2 ConfigMaps in the default nam
 trigger 2 Application updates.
 
 ```shell
-kubectl apply sample.yaml
+kubectl apply -f examples/sample.yaml
 ```
 
 2. **Run kube-trigger**
@@ -43,7 +47,9 @@ Standalone:
 In-Cluster:
 
 ```shell
-kubectl apply -f config/
+kubectl apply -f config/crd/
+kubectl apply -f config/definition/
+kubectl apply -f config/manager/
 ```
 
 3. **Watch ApplicationRevision changes** so that you can see what it does.