Add types and client for Resolution

config/300-resolutionrequest.yaml

@@ -26,8 +26,11 @@ spec:
     plural: resolutionrequests
     singular: resolutionrequest
     categories:
-    - all
-    - tekton
+      - tekton
+      - tekton-pipelines
+    shortNames:
+      - resolutionrequest
+      - resolutionrequests
   versions:
     - name: v1alpha1
       served: true
@@ -37,58 +40,14 @@ spec:
       schema:
         openAPIV3Schema:
           type: object
-          properties:
-            spec:
-              description: Spec holds the parameters for the request.
-              type: object
-              properties:
-                params:
-                  type: object
-                  x-kubernetes-preserve-unknown-fields: true
-            status:
-              description: Status receives the data of a completed request.
-              type: object
-              properties:
-                data:
-                  description: The resolved contents of the requested resource in-lined as a string.
-                  type: string
-                annotations:
-                  description: Annotations is additional Status fields for the Resource to save some additional State as well as convey more information to the user. This is roughly akin to Annotations on any k8s resource, just the reconciler conveying richer information outwards.
-                  type: object
-                  x-kubernetes-preserve-unknown-fields: true
-                conditions:
-                  description: Conditions the latest available observations of a resource's current state.
-                  type: array
-                  items:
-                    description: Conditions describe the success and completion state of the resource request.
-                    type: object
-                    required:
-                      - status
-                      - type
-                    properties:
-                      lastTransitionTime:
-                        description: LastTransitionTime is the last time the condition transitioned from one status to another. We use VolatileTime in place of metav1.Time to exclude this from creating equality.Semantic differences (all other things held constant).
-                        type: string
-                        format: date-time
-                      message:
-                        description: A human readable message indicating details about the transition.
-                        type: string
-                      reason:
-                        description: The reason for the condition's last transition.
-                        type: string
-                      severity:
-                        description: Severity with which to treat failures of this type of condition. When this is not specified, it defaults to Error.
-                        type: string
-                      status:
-                        description: Status of the condition, one of True, False, Unknown.
-                        type: string
-                      type:
-                        description: Type of condition.
-                        type: string
-                observedGeneration:
-                  description: ObservedGeneration is the 'Generation' of the Service that was last processed by the controller.
-                  type: integer
-                  format: int64
+          # One can use x-kubernetes-preserve-unknown-fields: true
+          # at the root of the schema (and inside any properties, additionalProperties)
+          # to get the traditional CRD behaviour that nothing is pruned, despite
+          # setting spec.preserveUnknownProperties: false.
+          #
+          # See https://kubernetes.io/blog/2019/06/20/crd-structural-schema/
+          # See issue: https://github.com/knative/serving/issues/912
+          x-kubernetes-preserve-unknown-fields: true
       additionalPrinterColumns:
         - name: Succeeded
           type: string