Update to ocm v0.14.0 crds

Signed-off-by: Tamal Saha <[email protected]>

hub/resourcedescriptors/addon.open-cluster-management.io/v1alpha1/addondeploymentconfigs.yaml

@@ -17,8 +17,9 @@ spec:
     version: v1alpha1
   validation:
     openAPIV3Schema:
-      description: AddOnDeploymentConfig represents a deployment configuration for
-        an add-on.
+      description: AddOnDeploymentConfig represents a configuration to customize the
+        deployments of an add-on. For example, you can specify the NodePlacement to
+        control the scheduling of the add-on agents.
       properties:
         apiVersion:
           description: 'APIVersion defines the versioned schema of this representation
@@ -161,6 +162,12 @@ spec:
               description: ProxyConfig holds proxy settings for add-on agent on the
                 managed cluster. Empty means no proxy settings is available.
               properties:
+                caBundle:
+                  description: CABundle is a CA certificate bundle to verify the proxy
+                    server. And it's only useful when HTTPSProxy is set and a HTTPS
+                    proxy server is specified.
+                  format: byte
+                  type: string
                 httpProxy:
                   description: HTTPProxy is the URL of the proxy for HTTP requests
                   type: string

hub/resourcedescriptors/addon.open-cluster-management.io/v1alpha1/addontemplates.yaml

@@ -286,11 +286,14 @@ spec:
                               server side apply with work-controller as the field
                               manager. If there is conflict, the related Applied condition
                               of manifest will be in the status of False with the
-                              reason of ApplyConflict.
+                              reason of ApplyConflict. ReadOnly type means the agent
+                              will only check the existence of the resource based
+                              on its metadata.
                             enum:
                             - Update
                             - CreateOnly
                             - ServerSideApply
+                            - ReadOnly
                             type: string
                         required:
                         - type
@@ -342,6 +345,7 @@ spec:
                           will use to create csr.
                         maxLength: 571
                         minLength: 5
+                        pattern: ^([a-z0-9][a-z0-9-]*[a-z0-9]\.)+[a-z]+\/[a-z0-9-\.]+$
                         type: string
                       signingCA:
                         description: 'SigningCA represents the reference of the secret

hub/resourcedescriptors/cluster.open-cluster-management.io/v1/managedclusters.yaml

@@ -18,16 +18,17 @@ spec:
   validation:
     openAPIV3Schema:
       description: "ManagedCluster represents the desired state and current status
-        of managed cluster. ManagedCluster is a cluster scoped resource. The name
-        is the cluster UID. \n The cluster join process follows a double opt-in process:
-        \n 1. Agent on managed cluster creates CSR on hub with cluster UID and agent
-        name. 2. Agent on managed cluster creates ManagedCluster on hub. 3. Cluster
-        admin on hub approves the CSR for UID and agent name of the ManagedCluster.
-        4. Cluster admin sets spec.acceptClient of ManagedCluster to true. 5. Cluster
-        admin on managed cluster creates credential of kubeconfig to hub. \n Once
-        the hub creates the cluster namespace, the Klusterlet agent on the ManagedCluster
-        pushes the credential to the hub to use against the kube-apiserver of the
-        ManagedCluster."
+        of a managed cluster. ManagedCluster is a cluster-scoped resource. The name
+        is the cluster UID. \n The cluster join process is a double opt-in process.
+        See the following join process steps: \n 1. The agent on the managed cluster
+        creates a CSR on the hub with the cluster UID and agent name. 2. The agent
+        on the managed cluster creates a ManagedCluster on the hub. 3. The cluster
+        admin on the hub cluster approves the CSR for the UID and agent name of the
+        ManagedCluster. 4. The cluster admin sets the spec.acceptClient of the ManagedCluster
+        to true. 5. The cluster admin on the managed cluster creates a credential
+        of the kubeconfig for the hub cluster. \n After the hub cluster creates the
+        cluster namespace, the klusterlet agent on the ManagedCluster pushes the credential
+        to the hub cluster to use against the kube-apiserver of the ManagedCluster."
       properties:
         apiVersion:
           description: 'APIVersion defines the versioned schema of this representation

hub/resourcedescriptors/cluster.open-cluster-management.io/v1beta1/placementdecisions.yaml

@@ -17,14 +17,14 @@ spec:
     version: v1beta1
   validation:
     openAPIV3Schema:
-      description: "PlacementDecision indicates a decision from a placement PlacementDecision
-        should has a label cluster.open-cluster-management.io/placement={placement
-        name} to reference a certain placement. \n If a placement has spec.numberOfClusters
-        specified, the total number of decisions contained in status.decisions of
-        PlacementDecisions should always be NumberOfClusters; otherwise, the total
-        number of decisions should be the number of ManagedClusters which match the
-        placement requirements. \n Some of the decisions might be empty when there
-        are no enough ManagedClusters meet the placement requirements."
+      description: "PlacementDecision indicates a decision from a placement. PlacementDecision
+        must have a cluster.open-cluster-management.io/placement={placement name}
+        label to reference a certain placement. \n If a placement has spec.numberOfClusters
+        specified, the total number of decisions contained in the status.decisions
+        of PlacementDecisions must be the same as NumberOfClusters. Otherwise, the
+        total number of decisions must equal the number of ManagedClusters that match
+        the placement requirements. \n Some of the decisions might be empty when there
+        are not enough ManagedClusters to meet the placement requirements."
       properties:
         apiVersion:
           description: 'APIVersion defines the versioned schema of this representation

hub/resourcedescriptors/cluster.open-cluster-management.io/v1beta1/placements.yaml

@@ -43,11 +43,11 @@ spec:
         ManagedClusterSets; 3. ManagedClusterSets are bound to workload namespaces;
         4. Namespace-scoped Placements specify a slice of ManagedClusterSets which
         select a working set of potential ManagedClusters; 5. Then Placements subselect
-        from that working set using label/claim selection. \n No ManagedCluster will
-        be selected if no ManagedClusterSet is bound to the placement namespace. User
-        is able to bind a ManagedClusterSet to a namespace by creating a ManagedClusterSetBinding
-        in that namespace if they have a RBAC rule to CREATE on the virtual subresource
-        of `managedclustersets/bind`. \n A slice of PlacementDecisions with label
+        from that working set using label/claim selection. \n A ManagedCluster will
+        not be selected if no ManagedClusterSet is bound to the placement namespace.
+        A user is able to bind a ManagedClusterSet to a namespace by creating a ManagedClusterSetBinding
+        in that namespace if they have an RBAC rule to CREATE on the virtual subresource
+        of `managedclustersets/bind`. \n A slice of PlacementDecisions with the label
         cluster.open-cluster-management.io/placement={placement name} will be created
         to represent the ManagedClusters selected by this placement. \n If a ManagedCluster
         is selected and added into the PlacementDecisions, other components may apply

hub/resourcedescriptors/cluster.open-cluster-management.io/v1beta2/managedclustersetbindings.yaml

@@ -27,11 +27,11 @@ spec:
   validation:
     openAPIV3Schema:
       description: ManagedClusterSetBinding projects a ManagedClusterSet into a certain
-        namespace. User is able to create a ManagedClusterSetBinding in a namespace
-        and bind it to a ManagedClusterSet if they have an RBAC rule to CREATE on
-        the virtual subresource of managedclustersets/bind. Workloads created in the
-        same namespace can only be distributed to ManagedClusters in ManagedClusterSets
-        bound in this namespace by higher level controllers.
+        namespace. You can create a ManagedClusterSetBinding in a namespace and bind
+        it to a ManagedClusterSet if both have a RBAC rules to CREATE on the virtual
+        subresource of managedclustersets/bind. Workloads that you create in the same
+        namespace can only be distributed to ManagedClusters in ManagedClusterSets
+        that are bound in this namespace by higher-level controllers.
       properties:
         apiVersion:
           description: 'APIVersion defines the versioned schema of this representation

hub/resourcedescriptors/cluster.open-cluster-management.io/v1beta2/managedclustersets.yaml

@@ -27,17 +27,17 @@ spec:
     version: v1beta2
   validation:
     openAPIV3Schema:
-      description: "ManagedClusterSet defines a group of ManagedClusters that user's
-        workload can run on. A workload can be defined to deployed on a ManagedClusterSet,
-        which mean: 1. The workload can run on any ManagedCluster in the ManagedClusterSet
-        2. The workload cannot run on any ManagedCluster outside the ManagedClusterSet
-        3. The service exposed by the workload can be shared in any ManagedCluster
-        in the ManagedClusterSet \n In order to assign a ManagedCluster to a certian
-        ManagedClusterSet, add a label with name `cluster.open-cluster-management.io/clusterset`
-        on the ManagedCluster to refers to the ManagedClusterSet. User is not allow
-        to add/remove this label on a ManagedCluster unless they have a RBAC rule
-        to CREATE on a virtual subresource of managedclustersets/join. In order to
-        update this label, user must have the permission on both the old and new ManagedClusterSet."
+      description: "ManagedClusterSet defines a group of ManagedClusters that you
+        can run workloads on. You can define a workload to be deployed on a ManagedClusterSet.
+        See the following options  for the workload: - The workload can run on any
+        ManagedCluster in the ManagedClusterSet - The workload cannot run on any ManagedCluster
+        outside the ManagedClusterSet - The service exposed by the workload can be
+        shared in any ManagedCluster in the ManagedClusterSet \n To assign a ManagedCluster
+        to a certain ManagedClusterSet, add a label with the name cluster.open-cluster-management.io/clusterset
+        on the ManagedCluster to refer to the ManagedClusterSet. You are not allowed
+        to add or remove this label on a ManagedCluster unless you have an RBAC rule
+        to CREATE on a virtual subresource of managedclustersets/join. To update this
+        label, you must have the permission on both the old and new ManagedClusterSet."
       properties:
         apiVersion:
           description: 'APIVersion defines the versioned schema of this representation

hub/resourcedescriptors/operator.open-cluster-management.io/v1/clustermanagers.yaml

@@ -282,7 +282,71 @@ spec:
               description: RegistrationImagePullSpec represents the desired image
                 of registration controller/webhook installed on hub.
               type: string
+            resourceRequirement:
+              description: ResourceRequirement specify QoS classes of deployments
+                managed by clustermanager. It applies to all the containers in the
+                deployments.
+              properties:
+                resourceRequirements:
+                  description: ResourceRequirements defines resource requests and
+                    limits when Type is ResourceQosClassResourceRequirement
+                  properties:
+                    claims:
+                      description: "Claims lists the names of resources, defined in
+                        spec.resourceClaims, that are used by this container. \n This
+                        is an alpha field and requires enabling the DynamicResourceAllocation
+                        feature gate. \n This field is immutable. It can only be set
+                        for containers."
+                      items:
+                        description: ResourceClaim references one entry in PodSpec.ResourceClaims.
+                        properties:
+                          name:
+                            description: Name must match the name of one entry in
+                              pod.spec.resourceClaims of the Pod where this field
+                              is used. It makes that resource available inside a container.
+                            type: string
+                        required:
+                        - name
+                        type: object
+                      type: array
+                      x-kubernetes-list-map-keys:
+                      - name
+                      x-kubernetes-list-type: map
+                    limits:
+                      additionalProperties:
+                        anyOf:
+                        - type: integer
+                        - type: string
+                        pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
+                        x-kubernetes-int-or-string: true
+                      description: 'Limits describes the maximum amount of compute
+                        resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/'
+                      type: object
+                    requests:
+                      additionalProperties:
+                        anyOf:
+                        - type: integer
+                        - type: string
+                        pattern: ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
+                        x-kubernetes-int-or-string: true
+                      description: 'Requests describes the minimum amount of compute
+                        resources required. If Requests is omitted for a container,
+                        it defaults to Limits if that is explicitly specified, otherwise
+                        to an implementation-defined value. Requests cannot exceed
+                        Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/'
+                      type: object
+                  type: object
+                type:
+                  default: Default
+                  enum:
+                  - Default
+                  - BestEffort
+                  - ResourceRequirement
+                  type: string
+              type: object
             workConfiguration:
+              default:
+                workDriver: kube
               description: WorkConfiguration contains the configuration of work
               properties:
                 featureGates:
@@ -316,6 +380,22 @@ spec:
                     - feature
                     type: object
                   type: array
+                workDriver:
+                  default: kube
+                  description: "WorkDriver represents the type of work driver. Possible
+                    values are \"kube\", \"mqtt\", or \"grpc\". If not provided, the
+                    default value is \"kube\". If set to non-\"kube\" drivers, the
+                    klusterlet need to use the same driver. and the driver configuration
+                    must be provided in a secret named \"work-driver-config\" in the
+                    namespace where the cluster manager is running, adhering to the
+                    following structure: config.yaml: | <driver-config-in-yaml> \n
+                    For detailed driver configuration, please refer to the sdk-go
+                    documentation: https://github.com/open-cluster-management-io/sdk-go/blob/main/pkg/cloudevents/README.md#supported-protocols-and-drivers"
+                  enum:
+                  - kube
+                  - mqtt
+                  - grpc
+                  type: string
               type: object
             workImagePullSpec:
               default: quay.io/open-cluster-management/work