AutoScaler is the Schema for the AutoScalers API. <no value>
Type
CRD
Group
castai.upbound.io
Version
v1alpha1
apiVersion: castai.upbound.io/v1alpha1
kind: AutoScaler
AutoScalerSpec defines the desired state of AutoScaler
No description provided.
autoscaler policy definitions to override current autoscaler settings
node downscaler defines policies for removing nodes based on the configured conditions.
defines whether Node Downscaler should opt in for removing empty worker nodes when possible.
defines the CAST AI Evictor component settings. Evictor watches the pods running in your cluster and looks for ways to compact them into fewer nodes, making nodes empty, which will be removed by the empty worker nodes policy.
policy defining whether autoscaler can use spot instances for provisioning additional workloads.
policy defining whether autoscaler can use spot backups instead of spot instances when spot instances are not available.
configure the handling of SPOT interruption predictions.
policy defining autoscaler's behavior when unschedulable pods were detected.
additional headroom based on cluster's total available capacity for on-demand nodes.
additional headroom based on cluster's total available capacity for spot nodes.
defines the node constraints that will be applied when autoscaling with Unschedulable Pods policy.
Reference to a EksClusterId in castai to populate clusterId.
Policies for referencing.
Selector for a EksClusterId in castai to populate clusterId.
Policies for selection.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
autoscaler policy definitions to override current autoscaler settings
node downscaler defines policies for removing nodes based on the configured conditions.
defines whether Node Downscaler should opt in for removing empty worker nodes when possible.
defines the CAST AI Evictor component settings. Evictor watches the pods running in your cluster and looks for ways to compact them into fewer nodes, making nodes empty, which will be removed by the empty worker nodes policy.
policy defining whether autoscaler can use spot instances for provisioning additional workloads.
policy defining whether autoscaler can use spot backups instead of spot instances when spot instances are not available.
configure the handling of SPOT interruption predictions.
policy defining autoscaler's behavior when unschedulable pods were detected.
additional headroom based on cluster's total available capacity for on-demand nodes.
additional headroom based on cluster's total available capacity for spot nodes.
defines the node constraints that will be applied when autoscaling with Unschedulable Pods policy.
Reference to a EksClusterId in castai to populate clusterId.
Policies for referencing.
Selector for a EksClusterId in castai to populate clusterId.
Policies for selection.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
AutoScalerStatus defines the observed state of AutoScaler.
No description provided.
autoscaler policy definitions to override current autoscaler settings
node downscaler defines policies for removing nodes based on the configured conditions.
defines whether Node Downscaler should opt in for removing empty worker nodes when possible.
defines the CAST AI Evictor component settings. Evictor watches the pods running in your cluster and looks for ways to compact them into fewer nodes, making nodes empty, which will be removed by the empty worker nodes policy.
policy defining whether autoscaler can use spot instances for provisioning additional workloads.
policy defining whether autoscaler can use spot backups instead of spot instances when spot instances are not available.
configure the handling of SPOT interruption predictions.
policy defining autoscaler's behavior when unschedulable pods were detected.
additional headroom based on cluster's total available capacity for on-demand nodes.
additional headroom based on cluster's total available capacity for spot nodes.
defines the node constraints that will be applied when autoscaling with Unschedulable Pods policy.
Conditions of the resource.
sample
apiVersion: castai.upbound.io/v1alpha1
kind: AutoScaler
metadata:
name: sample
spec:
forProvider:
autoscalerPoliciesJson: |
{
"enabled": true,
"unschedulablePods": {
"enabled": true
},
"spotInstances": {
"enabled": true,
"clouds": ["aws"],
"spotBackups": {
"enabled": true
},
"spotDiversityEnabled": false,
"spotDiversityPriceIncreaseLimitPercent": 20,
"spotInterruptionPredictions": {
"enabled": true,
"type": "AWSRebalanceRecommendations"
}
},
"nodeDownscaler": {
"enabled": true,
"emptyNodes": {
"enabled": true
},
"evictor": {
"aggressiveMode": false,
"cycleInterval": "5m10s",
"dryRun": false,
"enabled": true,
"nodeGracePeriodMinutes": 10,
"scopedMode": false
}
},
"clusterLimits": {
"cpu": {
"maxCores": 20,
"minCores": 1
},
"enabled": true
}
}
clusterIdSelector:
matchLabels:
cast-ai-cluster: sample-cluster
providerConfigRef:
name: default
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.