Skip to content

Commit 26ae98e

Browse files
tkashemtkashem
committed
run make update
1 parent 4420193 commit 26ae98e

File tree

27 files changed

+1049
-58
lines changed

27 files changed

+1049
-58
lines changed

‎config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_schedulers-Hypershift-CustomNoUpgrade.crd.yaml‎

Lines changed: 143 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,143 @@
1+
apiVersion: apiextensions.k8s.io/v1
2+
kind: CustomResourceDefinition
3+
metadata:
4+
annotations:
5+
api-approved.openshift.io: https://github.com/openshift/api/pull/470
6+
api.openshift.io/merged-by-featuregates: "true"
7+
include.release.openshift.io/ibm-cloud-managed: "true"
8+
release.openshift.io/bootstrap-required: "true"
9+
release.openshift.io/feature-set: CustomNoUpgrade
10+
name: schedulers.config.openshift.io
11+
spec:
12+
group: config.openshift.io
13+
names:
14+
kind: Scheduler
15+
listKind: SchedulerList
16+
plural: schedulers
17+
singular: scheduler
18+
scope: Cluster
19+
versions:
20+
- name: v1
21+
schema:
22+
openAPIV3Schema:
23+
description: |-
24+
Scheduler holds cluster-wide config information to run the Kubernetes Scheduler
25+
and influence its placement decisions. The canonical name for this config is `cluster`.
26+
27+
Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).
28+
properties:
29+
apiVersion:
30+
description: |-
31+
APIVersion defines the versioned schema of this representation of an object.
32+
Servers should convert recognized schemas to the latest internal value, and
33+
may reject unrecognized values.
34+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
35+
type: string
36+
kind:
37+
description: |-
38+
Kind is a string value representing the REST resource this object represents.
39+
Servers may infer this from the endpoint the client submits requests to.
40+
Cannot be updated.
41+
In CamelCase.
42+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
43+
type: string
44+
metadata:
45+
type: object
46+
spec:
47+
description: spec holds user settable values for configuration
48+
properties:
49+
defaultNodeSelector:
50+
description: |-
51+
defaultNodeSelector helps set the cluster-wide default node selector to
52+
restrict pod placement to specific nodes. This is applied to the pods
53+
created in all namespaces and creates an intersection with any existing
54+
nodeSelectors already set on a pod, additionally constraining that pod's selector.
55+
For example,
56+
defaultNodeSelector: "type=user-node,region=east" would set nodeSelector
57+
field in pod spec to "type=user-node,region=east" to all pods created
58+
in all namespaces. Namespaces having project-wide node selectors won't be
59+
impacted even if this field is set. This adds an annotation section to
60+
the namespace.
61+
For example, if a new namespace is created with
62+
node-selector='type=user-node,region=east',
63+
the annotation openshift.io/node-selector: type=user-node,region=east
64+
gets added to the project. When the openshift.io/node-selector annotation
65+
is set on the project the value is used in preference to the value we are setting
66+
for defaultNodeSelector field.
67+
For instance,
68+
openshift.io/node-selector: "type=user-node,region=west" means
69+
that the default of "type=user-node,region=east" set in defaultNodeSelector
70+
would not be applied.
71+
type: string
72+
mastersSchedulable:
73+
description: |-
74+
mastersSchedulable allows masters nodes to be schedulable. When this flag is
75+
turned on, all the master nodes in the cluster will be made schedulable,
76+
so that workload pods can run on them. The default value for this field is false,
77+
meaning none of the master nodes are schedulable.
78+
Important Note: Once the workload pods start running on the master nodes,
79+
extreme care must be taken to ensure that cluster-critical control plane components
80+
are not impacted.
81+
Please turn on this field after doing due diligence.
82+
type: boolean
83+
policy:
84+
description: |-
85+
DEPRECATED: the scheduler Policy API has been deprecated and will be removed in a future release.
86+
policy is a reference to a ConfigMap containing scheduler policy which has
87+
user specified predicates and priorities. If this ConfigMap is not available
88+
scheduler will default to use DefaultAlgorithmProvider.
89+
The namespace for this configmap is openshift-config.
90+
properties:
91+
name:
92+
description: name is the metadata.name of the referenced config
93+
map
94+
type: string
95+
required:
96+
- name
97+
type: object
98+
profile:
99+
description: |-
100+
profile sets which scheduling profile should be set in order to configure scheduling
101+
decisions for new pods.
102+
103+
Valid values are "LowNodeUtilization", "HighNodeUtilization", "NoScoring"
104+
Defaults to "LowNodeUtilization"
105+
enum:
106+
- ""
107+
- LowNodeUtilization
108+
- HighNodeUtilization
109+
- NoScoring
110+
type: string
111+
profileCustomizations:
112+
description: |-
113+
Deprecated: no longer needed, DRA is GA and is enabled by default in the cluster
114+
profileCustomizations contains configuration for modifying the default behavior of existing scheduler profiles.
115+
properties:
116+
dynamicResourceAllocation:
117+
description: |-
118+
dynamicResourceAllocation allows to enable or disable dynamic resource allocation within the scheduler.
119+
Dynamic resource allocation is an API for requesting and sharing resources between pods and containers inside a pod.
120+
Third-party resource drivers are responsible for tracking and allocating resources.
121+
Different kinds of resources support arbitrary parameters for defining requirements and initialization.
122+
Valid values are Enabled, Disabled and omitted.
123+
When omitted, this means no opinion and the platform is left to choose a reasonable default,
124+
which is subject to change over time.
125+
The current default is Disabled.
126+
enum:
127+
- ""
128+
- Enabled
129+
- Disabled
130+
type: string
131+
type: object
132+
type: object
133+
status:
134+
description: status holds observed values from the cluster. They may not
135+
be overridden.
136+
type: object
137+
required:
138+
- spec
139+
type: object
140+
served: true
141+
storage: true
142+
subresources:
143+
status: {}

‎config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_schedulers-TechPreviewNoUpgrade.crd.yaml‎ renamed to ‎config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_schedulers-Hypershift-Default.crd.yaml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,8 @@ metadata:
55
api-approved.openshift.io: https://github.com/openshift/api/pull/470
66
api.openshift.io/merged-by-featuregates: "true"
77
include.release.openshift.io/ibm-cloud-managed: "true"
8-
include.release.openshift.io/self-managed-high-availability: "true"
98
release.openshift.io/bootstrap-required: "true"
10-
release.openshift.io/feature-set: TechPreviewNoUpgrade
9+
release.openshift.io/feature-set: Default
1110
name: schedulers.config.openshift.io
1211
spec:
1312
group: config.openshift.io
@@ -110,8 +109,9 @@ spec:
110109
- NoScoring
111110
type: string
112111
profileCustomizations:
113-
description: profileCustomizations contains configuration for modifying
114-
the default behavior of existing scheduler profiles.
112+
description: |-
113+
Deprecated: no longer needed, DRA is GA and is enabled by default in the cluster
114+
profileCustomizations contains configuration for modifying the default behavior of existing scheduler profiles.
115115
properties:
116116
dynamicResourceAllocation:
117117
description: |-

‎config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_schedulers-Hypershift-DevPreviewNoUpgrade.crd.yaml‎

Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
apiVersion: apiextensions.k8s.io/v1
2+
kind: CustomResourceDefinition
3+
metadata:
4+
annotations:
5+
api-approved.openshift.io: https://github.com/openshift/api/pull/470
6+
api.openshift.io/merged-by-featuregates: "true"
7+
include.release.openshift.io/ibm-cloud-managed: "true"
8+
release.openshift.io/bootstrap-required: "true"
9+
release.openshift.io/feature-set: DevPreviewNoUpgrade
10+
name: schedulers.config.openshift.io
11+
spec:
12+
group: config.openshift.io
13+
names:
14+
kind: Scheduler
15+
listKind: SchedulerList
16+
plural: schedulers
17+
singular: scheduler
18+
scope: Cluster
19+
versions:
20+
- name: v1
21+
schema:
22+
openAPIV3Schema:
23+
description: |-
24+
Scheduler holds cluster-wide config information to run the Kubernetes Scheduler
25+
and influence its placement decisions. The canonical name for this config is `cluster`.
26+
27+
Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).
28+
properties:
29+
apiVersion:
30+
description: |-
31+
APIVersion defines the versioned schema of this representation of an object.
32+
Servers should convert recognized schemas to the latest internal value, and
33+
may reject unrecognized values.
34+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
35+
type: string
36+
kind:
37+
description: |-
38+
Kind is a string value representing the REST resource this object represents.
39+
Servers may infer this from the endpoint the client submits requests to.
40+
Cannot be updated.
41+
In CamelCase.
42+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
43+
type: string
44+
metadata:
45+
type: object
46+
spec:
47+
description: spec holds user settable values for configuration
48+
properties:
49+
defaultNodeSelector:
50+
description: |-
51+
defaultNodeSelector helps set the cluster-wide default node selector to
52+
restrict pod placement to specific nodes. This is applied to the pods
53+
created in all namespaces and creates an intersection with any existing
54+
nodeSelectors already set on a pod, additionally constraining that pod's selector.
55+
For example,
56+
defaultNodeSelector: "type=user-node,region=east" would set nodeSelector
57+
field in pod spec to "type=user-node,region=east" to all pods created
58+
in all namespaces. Namespaces having project-wide node selectors won't be
59+
impacted even if this field is set. This adds an annotation section to
60+
the namespace.
61+
For example, if a new namespace is created with
62+
node-selector='type=user-node,region=east',
63+
the annotation openshift.io/node-selector: type=user-node,region=east
64+
gets added to the project. When the openshift.io/node-selector annotation
65+
is set on the project the value is used in preference to the value we are setting
66+
for defaultNodeSelector field.
67+
For instance,
68+
openshift.io/node-selector: "type=user-node,region=west" means
69+
that the default of "type=user-node,region=east" set in defaultNodeSelector
70+
would not be applied.
71+
type: string
72+
mastersSchedulable:
73+
description: |-
74+
mastersSchedulable allows masters nodes to be schedulable. When this flag is
75+
turned on, all the master nodes in the cluster will be made schedulable,
76+
so that workload pods can run on them. The default value for this field is false,
77+
meaning none of the master nodes are schedulable.
78+
Important Note: Once the workload pods start running on the master nodes,
79+
extreme care must be taken to ensure that cluster-critical control plane components
80+
are not impacted.
81+
Please turn on this field after doing due diligence.
82+
type: boolean
83+
policy:
84+
description: |-
85+
DEPRECATED: the scheduler Policy API has been deprecated and will be removed in a future release.
86+
policy is a reference to a ConfigMap containing scheduler policy which has
87+
user specified predicates and priorities. If this ConfigMap is not available
88+
scheduler will default to use DefaultAlgorithmProvider.
89+
The namespace for this configmap is openshift-config.
90+
properties:
91+
name:
92+
description: name is the metadata.name of the referenced config
93+
map
94+
type: string
95+
required:
96+
- name
97+
type: object
98+
profile:
99+
description: |-
100+
profile sets which scheduling profile should be set in order to configure scheduling
101+
decisions for new pods.
102+
103+
Valid values are "LowNodeUtilization", "HighNodeUtilization", "NoScoring"
104+
Defaults to "LowNodeUtilization"
105+
enum:
106+
- ""
107+
- LowNodeUtilization
108+
- HighNodeUtilization
109+
- NoScoring
110+
type: string
111+
type: object
112+
status:
113+
description: status holds observed values from the cluster. They may not
114+
be overridden.
115+
type: object
116+
required:
117+
- spec
118+
type: object
119+
served: true
120+
storage: true
121+
subresources:
122+
status: {}

0 commit comments

Comments
 (0)