diff --git a/examples/npwg-demo-1/01_crd.yml b/examples/npwg-demo-1/01_crd.yml
index cb1486560..7b74a5f04 100644
--- a/examples/npwg-demo-1/01_crd.yml
+++ b/examples/npwg-demo-1/01_crd.yml
@@ -2,21 +2,29 @@ apiVersion: apiextensions.k8s.io/v1beta1
 kind: CustomResourceDefinition
 metadata:
   # name must match the spec fields below, and be in the form: <plural>.<group>
-  name: networks.kubernetes.cni.cncf.io
+  name: network-attachment-definitions.k8s.cni.cncf.io
 spec:
   # group name to use for REST API: /apis/<group>/<version>
-  group: kubernetes.cni.cncf.io
+  group: k8s.cni.cncf.io
   # version name to use for REST API: /apis/<group>/<version>
   version: v1
   # either Namespaced or Cluster
   scope: Namespaced
   names:
     # plural name to be used in the URL: /apis/<group>/<version>/<plural>
-    plural: networks
+    plural: network-attachment-definitions
     # singular name to be used as an alias on the CLI and for display
-    singular: network
+    singular: network-attachment-definition
     # kind is normally the CamelCased singular type. Your resource manifests use this.
-    kind: Network
+    kind: NetworkAttachmentDefinition
     # shortNames allow shorter string to match your resource on the CLI
     shortNames:
-    - net
+    - net-attach-def
+  validation:
+    openAPIV3Schema:
+      properties:
+        spec:
+          properties:
+            config:
+                 type: string
+
diff --git a/examples/npwg-demo-1/02_clusterrole.yml b/examples/npwg-demo-1/02_clusterrole.yml
index 635ba0c1e..d374cca51 100644
--- a/examples/npwg-demo-1/02_clusterrole.yml
+++ b/examples/npwg-demo-1/02_clusterrole.yml
@@ -2,7 +2,7 @@
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
 metadata:
-  name: multus-crd-overpowered
+  name: multus
 rules:
 - apiGroups:
   - '*'