ClusterAutoscaler is the Schema for the clusterautoscalers API
ClusterAutoscaler is the Schema for the clusterautoscalers API
object
Property | Type | Description |
---|---|---|
|
|
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
|
|
Kind is a string value representing the ReST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
|
Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata |
|
|
|
Desired state of ClusterAutoscaler resource |
|
|
Most recently observed status of ClusterAutoscaler resource |
Desired state of ClusterAutoscaler resource
object
Property | Type | Description |
---|---|---|
|
|
BalanceSimilarNodeGroups enables/disables the |
|
|
BalancingIgnoredLabels sets "--balancing-ignore-label <label name>" flag on cluster-autoscaler for each listed label. This option specifies labels that cluster autoscaler should ignore when considering node group similarity. For example, if you have nodes with "topology.ebs.csi.aws.com/zone" label, you can add name of this label here to prevent cluster autoscaler from spliting nodes into different node groups based on its value. |
|
|
enables/Disables |
|
|
Sets the autoscaler log level. Default value is 1, level 4 is recommended for DeBUGGING and level 6 will enable almost everything.
This option has priority over log level set by the |
|
|
Maximum time CA waits for node to be provisioned |
|
|
Gives pods graceful termination time before scaling down |
|
|
To allow users to schedule "best-effort" pods, which shouldn’t trigger Cluster Autoscaler actions, but only run when there are spare resources available, More info: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#how-does-cluster-autoscaler-work-with-pod-priority-and-preemption |
|
|
Constraints of autoscaling resources |
|
|
Configuration of scale down operation |
|
|
enables/Disables |
Constraints of autoscaling resources
object
Property | Type | Description |
---|---|---|
|
|
Minimum and maximum number of cores in cluster, in the format <min>:<max>. Cluster autoscaler will not scale the cluster beyond these numbers. |
|
|
Minimum and maximum number of different GPUs in cluster, in the format <gpu_type>:<min>:<max>. Cluster autoscaler will not scale the cluster beyond these numbers. Can be passed multiple times. |
|
|
|
|
|
Maximum number of nodes in all node groups. Cluster autoscaler will not grow the cluster beyond this number. |
|
|
Minimum and maximum number of gigabytes of memory in cluster, in the format <min>:<max>. Cluster autoscaler will not scale the cluster beyond these numbers. |
Minimum and maximum number of cores in cluster, in the format <min>:<max>. Cluster autoscaler will not scale the cluster beyond these numbers.
object
max
min
Property | Type | Description |
---|---|---|
|
|
|
|
|
Minimum and maximum number of different GPUs in cluster, in the format <gpu_type>:<min>:<max>. Cluster autoscaler will not scale the cluster beyond these numbers. Can be passed multiple times.
array
object
max
min
type
Property | Type | Description |
---|---|---|
|
|
|
|
|
|
|
|
The type of GPU to associate with the minimum and maximum limits. This value is used by the Cluster Autoscaler to identify Nodes that will have GPU capacity by searching for it as a label value on the Node objects. For example, Nodes that carry the label key |
Minimum and maximum number of gigabytes of memory in cluster, in the format <min>:<max>. Cluster autoscaler will not scale the cluster beyond these numbers.
object
max
min
Property | Type | Description |
---|---|---|
|
|
|
|
|
Configuration of scale down operation
object
enabled
Property | Type | Description |
---|---|---|
|
|
How long after scale up that scale down evaluation resumes |
|
|
How long after node deletion that scale down evaluation resumes, defaults to scan-interval |
|
|
How long after scale down failure that scale down evaluation resumes |
|
|
Should CA scale down the cluster |
|
|
How long a node should be unneeded before it is eligible for scale down |
|
|
Node utilization level, defined as sum of requested resources divided by capacity, below which a node can be considered for scale down |
The following API endpoints are available:
/apis/autoscaling.openshift.io/v1/clusterautoscalers
DeLeTe
: delete collection of ClusterAutoscaler
GeT
: list objects of kind ClusterAutoscaler
POST
: create a ClusterAutoscaler
/apis/autoscaling.openshift.io/v1/clusterautoscalers/{name}
DeLeTe
: delete a ClusterAutoscaler
GeT
: read the specified ClusterAutoscaler
PATCH
: partially update the specified ClusterAutoscaler
PUT
: replace the specified ClusterAutoscaler
/apis/autoscaling.openshift.io/v1/clusterautoscalers/{name}/status
GeT
: read status of the specified ClusterAutoscaler
PATCH
: partially update status of the specified ClusterAutoscaler
PUT
: replace status of the specified ClusterAutoscaler
DeLeTe
delete collection of ClusterAutoscaler
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
empty |
GeT
list objects of kind ClusterAutoscaler
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
empty |
POST
create a ClusterAutoscaler
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized |
empty |
Parameter | Type | Description |
---|---|---|
|
|
name of the ClusterAutoscaler |
DeLeTe
delete a ClusterAutoscaler
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
HTTP code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized |
empty |
GeT
read the specified ClusterAutoscaler
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
empty |
PATCH
partially update the specified ClusterAutoscaler
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
empty |
PUT
replace the specified ClusterAutoscaler
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized |
empty |
Parameter | Type | Description |
---|---|---|
|
|
name of the ClusterAutoscaler |
GeT
read status of the specified ClusterAutoscaler
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
empty |
PATCH
partially update status of the specified ClusterAutoscaler
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
empty |
PUT
replace status of the specified ClusterAutoscaler
Parameter | Type | Description |
---|---|---|
|
|
When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized |
empty |