Regen

openshift · Feb 8, 2024 · ccda9db · ccda9db
1 parent 0ef5f6d
commit ccda9db
Show file tree

Hide file tree

Showing 7 changed files with 57 additions and 31 deletions.
diff --git a/config/v1/0000_10_config-operator_01_scheduler-CustomNoUpgrade.crd.yaml b/config/v1/0000_10_config-operator_01_scheduler-CustomNoUpgrade.crd.yaml
@@ -96,13 +96,20 @@ spec:
                 - NoScoring
                 type: string
               profileCustomizations:
-                description: ProfileCustomizations contains various parameters for
-                  modifying the default behavior of existing profiles.
+                description: profileCustomizations contains configuration for modifying
+                  the default behavior of existing scheduler profiles.
                 properties:
                   dynamicResourceAllocation:
-                    description: experimentalDynamicResourceAllocation enables/disables
-                      dynamic resource allocation feature. Set to "" by default which
-                      means disabled. The default is subject to change.
+                    description: dynamicResourceAllocation allows to enable or disable
+                      dynamic resource allocation within the scheduler. Dynamic resource
+                      allocation is an API for requesting and sharing resources between
+                      pods and containers inside a pod. Third-party resource drivers
+                      are responsible for tracking and allocating resources. Different
+                      kinds of resources support arbitrary parameters for defining
+                      requirements and initialization. Valid values are Enabled, Disabled
+                      and omitted. When omitted, this means no opinion and the platform
+                      is left to choose a reasonable default, which is subject to
+                      change over time. The current default is Disabled.
                     enum:
                     - ""
                     - Enabled

diff --git a/config/v1/0000_10_config-operator_01_scheduler-TechPreviewNoUpgrade.crd.yaml b/config/v1/0000_10_config-operator_01_scheduler-TechPreviewNoUpgrade.crd.yaml
@@ -96,13 +96,20 @@ spec:
                 - NoScoring
                 type: string
               profileCustomizations:
-                description: ProfileCustomizations contains various parameters for
-                  modifying the default behavior of existing profiles.
+                description: profileCustomizations contains configuration for modifying
+                  the default behavior of existing scheduler profiles.
                 properties:
                   dynamicResourceAllocation:
-                    description: experimentalDynamicResourceAllocation enables/disables
-                      dynamic resource allocation feature. Set to "" by default which
-                      means disabled. The default is subject to change.
+                    description: dynamicResourceAllocation allows to enable or disable
+                      dynamic resource allocation within the scheduler. Dynamic resource
+                      allocation is an API for requesting and sharing resources between
+                      pods and containers inside a pod. Third-party resource drivers
+                      are responsible for tracking and allocating resources. Different
+                      kinds of resources support arbitrary parameters for defining
+                      requirements and initialization. Valid values are Enabled, Disabled
+                      and omitted. When omitted, this means no opinion and the platform
+                      is left to choose a reasonable default, which is subject to
+                      change over time. The current default is Disabled.
                     enum:
                     - ""
                     - Enabled

diff --git a/config/v1/zz_generated.swagger_doc_generated.go b/config/v1/zz_generated.swagger_doc_generated.go
diff --git a/openapi/generated_openapi/zz_generated.openapi.go b/openapi/generated_openapi/zz_generated.openapi.go
diff --git a/openapi/openapi.json b/openapi/openapi.json
@@ -9380,8 +9380,9 @@
       "type": "object",
       "properties": {
         "dynamicResourceAllocation": {
-          "description": "experimentalDynamicResourceAllocation enables/disables dynamic resource allocation feature. Set to \"\" by default which means disabled. The default is subject to change.",
-          "type": "string"
+          "description": "dynamicResourceAllocation allows to enable or disable dynamic resource allocation within the scheduler. Dynamic resource allocation is an API for requesting and sharing resources between pods and containers inside a pod. Third-party resource drivers are responsible for tracking and allocating resources. Different kinds of resources support arbitrary parameters for defining requirements and initialization. Valid values are Enabled, Disabled and omitted. When omitted, this means no opinion and the platform is left to choose a reasonable default, which is subject to change over time. The current default is Disabled.",
+          "type": "string",
+          "default": ""
         }
       }
     },
@@ -9908,9 +9909,6 @@
     },
     "com.github.openshift.api.config.v1.SchedulerSpec": {
       "type": "object",
-      "required": [
-        "profileCustomizations"
-      ],
       "properties": {
         "defaultNodeSelector": {
           "description": "defaultNodeSelector helps set the cluster-wide default node selector to restrict pod placement to specific nodes. This is applied to the pods created in all namespaces and creates an intersection with any existing nodeSelectors already set on a pod, additionally constraining that pod's selector. For example, defaultNodeSelector: \"type=user-node,region=east\" would set nodeSelector field in pod spec to \"type=user-node,region=east\" to all pods created in all namespaces. Namespaces having project-wide node selectors won't be impacted even if this field is set. This adds an annotation section to the namespace. For example, if a new namespace is created with node-selector='type=user-node,region=east', the annotation openshift.io/node-selector: type=user-node,region=east gets added to the project. When the openshift.io/node-selector annotation is set on the project the value is used in preference to the value we are setting for defaultNodeSelector field. For instance, openshift.io/node-selector: \"type=user-node,region=west\" means that the default of \"type=user-node,region=east\" set in defaultNodeSelector would not be applied.",
@@ -9931,7 +9929,7 @@
           "type": "string"
         },
         "profileCustomizations": {
-          "description": "ProfileCustomizations contains various parameters for modifying the default behavior of existing profiles.",
+          "description": "profileCustomizations contains configuration for modifying the default behavior of existing scheduler profiles.",
           "default": {},
           "$ref": "#/definitions/com.github.openshift.api.config.v1.ProfileCustomizations"
         }

diff --git a/payload-manifests/crds/0000_10_config-operator_01_scheduler-CustomNoUpgrade.crd.yaml b/payload-manifests/crds/0000_10_config-operator_01_scheduler-CustomNoUpgrade.crd.yaml
@@ -96,13 +96,20 @@ spec:
                 - NoScoring
                 type: string
               profileCustomizations:
-                description: ProfileCustomizations contains various parameters for
-                  modifying the default behavior of existing profiles.
+                description: profileCustomizations contains configuration for modifying
+                  the default behavior of existing scheduler profiles.
                 properties:
                   dynamicResourceAllocation:
-                    description: experimentalDynamicResourceAllocation enables/disables
-                      dynamic resource allocation feature. Set to "" by default which
-                      means disabled. The default is subject to change.
+                    description: dynamicResourceAllocation allows to enable or disable
+                      dynamic resource allocation within the scheduler. Dynamic resource
+                      allocation is an API for requesting and sharing resources between
+                      pods and containers inside a pod. Third-party resource drivers
+                      are responsible for tracking and allocating resources. Different
+                      kinds of resources support arbitrary parameters for defining
+                      requirements and initialization. Valid values are Enabled, Disabled
+                      and omitted. When omitted, this means no opinion and the platform
+                      is left to choose a reasonable default, which is subject to
+                      change over time. The current default is Disabled.
                     enum:
                     - ""
                     - Enabled

diff --git a/payload-manifests/crds/0000_10_config-operator_01_scheduler-TechPreviewNoUpgrade.crd.yaml b/payload-manifests/crds/0000_10_config-operator_01_scheduler-TechPreviewNoUpgrade.crd.yaml
@@ -96,13 +96,20 @@ spec:
                 - NoScoring
                 type: string
               profileCustomizations:
-                description: ProfileCustomizations contains various parameters for
-                  modifying the default behavior of existing profiles.
+                description: profileCustomizations contains configuration for modifying
+                  the default behavior of existing scheduler profiles.
                 properties:
                   dynamicResourceAllocation:
-                    description: experimentalDynamicResourceAllocation enables/disables
-                      dynamic resource allocation feature. Set to "" by default which
-                      means disabled. The default is subject to change.
+                    description: dynamicResourceAllocation allows to enable or disable
+                      dynamic resource allocation within the scheduler. Dynamic resource
+                      allocation is an API for requesting and sharing resources between
+                      pods and containers inside a pod. Third-party resource drivers
+                      are responsible for tracking and allocating resources. Different
+                      kinds of resources support arbitrary parameters for defining
+                      requirements and initialization. Valid values are Enabled, Disabled
+                      and omitted. When omitted, this means no opinion and the platform
+                      is left to choose a reasonable default, which is subject to
+                      change over time. The current default is Disabled.
                     enum:
                     - ""
                     - Enabled