Make ClusterUsage actually cluster scoped

Now with more cluster!

(Also, give it a status subresource.)

Signed-off-by: Nic Cope <nicc@rk0n.org>

apis/protection/v1beta1/clusterusage_types.go

@@ -35,8 +35,8 @@ import (
 // +kubebuilder:printcolumn:name="DETAILS",type="string",JSONPath=".metadata.annotations.crossplane\\.io/usage-details"
 // +kubebuilder:printcolumn:name="READY",type="string",JSONPath=".status.conditions[?(@.type=='Ready')].status"
 // +kubebuilder:printcolumn:name="AGE",type="date",JSONPath=".metadata.creationTimestamp"
-// +kubebuilder:resource:categories=crossplane
+// +kubebuilder:resource:scope=Cluster,categories=crossplane
-// +kubebuilder:scope=cluster,subresource:status
+// +kubebuilder:subresource:status
 type ClusterUsage struct {
 	metav1.TypeMeta   `json:",inline"`
 	metav1.ObjectMeta `json:"metadata,omitempty"`

cluster/crds/protection.crossplane.io_clusterusages.yaml

@@ -14,7 +14,7 @@ spec:
     listKind: ClusterUsageList
     plural: clusterusages
     singular: clusterusage
-  scope: Namespaced
+  scope: Cluster
   versions:
   - additionalPrinterColumns:
     - jsonPath: .metadata.annotations.crossplane\.io/usage-details
@@ -212,4 +212,5 @@ spec:
         type: object
     served: true
     storage: true
-    subresources: {}
+    subresources:
+      status: {}