Reorder cluster role API groups in kube-state-metrics.libsonnet

Put customresourcedefinitions first, and then the specific CRD types
can come after that.

Signed-off-by: Dan Winship <[email protected]>

Author: danwinship

assets/kube-state-metrics/cluster-role.yaml

@@ -129,17 +129,17 @@ rules:
   - list
   - watch
 - apiGroups:
-  - autoscaling.k8s.io
+  - apiextensions.k8s.io
   resources:
-  - verticalpodautoscalers
+  - customresourcedefinitions
   verbs:
+  - get
   - list
   - watch
 - apiGroups:
-  - apiextensions.k8s.io
+  - autoscaling.k8s.io
   resources:
-  - customresourcedefinitions
+  - verticalpodautoscalers
   verbs:
-  - get
   - list
   - watch

jsonnet/components/kube-state-metrics.libsonnet

@@ -42,18 +42,18 @@ function(params)
 
     clusterRole+: {
       rules+: [
-        {
-          apiGroups: ['autoscaling.k8s.io'],
-          resources: ['verticalpodautoscalers'],
-          verbs: ['list', 'watch'],
-        },
         // CRD read permissions are required for kube-state-metrics to support the CRS feature-set.
         // Refer: https://github.com/kubernetes/kube-state-metrics/pull/1851/files#diff-916e6863e1245c673b4e5965c98dc27bafbd72650fdb38ce65ea73ee6304e027R45-R47
         {
           apiGroups: ['apiextensions.k8s.io'],
           resources: ['customresourcedefinitions'],
           verbs: ['get', 'list', 'watch'],
         },
+        {
+          apiGroups: ['autoscaling.k8s.io'],
+          resources: ['verticalpodautoscalers'],
+          verbs: ['list', 'watch'],
+        },
       ],
     },
 

manifests/0000_50_cluster-monitoring-operator_02-role.yaml

@@ -360,18 +360,18 @@ rules:
   - list
   - watch
 - apiGroups:
-  - autoscaling.k8s.io
+  - apiextensions.k8s.io
   resources:
-  - verticalpodautoscalers
+  - customresourcedefinitions
   verbs:
+  - get
   - list
   - watch
 - apiGroups:
-  - apiextensions.k8s.io
+  - autoscaling.k8s.io
   resources:
-  - customresourcedefinitions
+  - verticalpodautoscalers
   verbs:
-  - get
   - list
   - watch
 - apiGroups: