]
            },
            {
              "resource": "resourceslices",
              "responseKind": {
                "group": "",
                "kind": "ResourceSlice",
                "version": ""
              },
              "scope": "Cluster",
              "singularResource": "resourceslice",
              "verbs": [
                "create",
                "delete",

              ]
            },
            {
              "resource": "resourceslices",
              "responseKind": {
                "group": "",
                "kind": "ResourceSlice",
                "version": ""
              },
              "scope": "Cluster",
              "singularResource": "resourceslice",
              "verbs": [
                "create",
                "delete",

	// assigned to such a claim. Alternatively, claim allocation state
	// could also get tracked across pod scheduling cycles, but that
	// - adds complexity (need to carefully sync state with informer events
	//   for claims and ResourceSlices)
	// - would make integration with cluster autoscaler harder because it would need
	//   to trigger informer callbacks.
	//
	// When implementing cluster autoscaler support, this assume cache or

	apiResource := resourceapi.SchemeGroupVersion.WithResource("resourceslices")
	nodename := "mynode"
	mynode := &user.DefaultInfo{Name: "system:node:" + nodename, Groups: []string{"system:nodes"}}
	err := "can only create ResourceSlice with the same NodeName as the requesting node"

	sliceNode := &resourceapi.ResourceSlice{
		ObjectMeta: metav1.ObjectMeta{
			Name: "something",
		},