Azure Kubernetes Service · Schema
ManagedClusterAutoScalerProfile
Parameters to be applied to the cluster-autoscaler.
AzureCloudContainersDevOpsKubernetesOrchestration
Properties
| Name | Type | Description |
|---|---|---|
| balance-similar-node-groups | string | Detects similar node pools and balances the number of nodes between them. |
| daemonset-eviction-for-empty-nodes | boolean | If set to true, all daemonset pods on empty nodes will be evicted before deletion of the node. |
| daemonset-eviction-for-occupied-nodes | boolean | If set to true, all daemonset pods on occupied nodes will be evicted before deletion of the node. |
| expander | string | The expander to use when scaling up. |
| max-empty-bulk-delete | string | The maximum number of empty nodes that can be deleted at the same time. |
| max-graceful-termination-sec | string | Maximum number of seconds the cluster autoscaler waits for pod termination when trying to scale down a node. |
| max-node-provision-time | string | The maximum time the autoscaler waits for a node to be provisioned. |
| max-total-unready-percentage | string | Maximum percentage of unready nodes in the cluster. After this percentage is exceeded, the cluster autoscaler halts operations. |
| new-pod-scale-up-delay | string | For scenarios like burst/batch scale where you do not want CA to act before the kubernetes scheduler could schedule all the pods. |
| ok-total-unready-count | string | Number of allowed unready nodes, irrespective of max-total-unready-percentage. |
| scan-interval | string | How often the cluster is reevaluated for scale up or down. |
| scale-down-delay-after-add | string | How long after scale up that scale down evaluation resumes. |
| scale-down-delay-after-delete | string | How long after node deletion that scale down evaluation resumes. |
| scale-down-delay-after-failure | string | How long after scale down failure that scale down evaluation resumes. |
| scale-down-unneeded-time | string | How long a node should be unneeded before it is eligible for scale down. |
| scale-down-unready-time | string | How long an unready node should be unneeded before it is eligible for scale down. |
| scale-down-utilization-threshold | string | Node utilization level, defined as sum of requested resources divided by capacity, below which a node can be considered for scale down. |
| skip-nodes-with-local-storage | string | Whether the cluster autoscaler will skip deleting nodes with pods with local storage. |
| skip-nodes-with-system-pods | string | Whether the cluster autoscaler will skip deleting nodes with pods from kube-system (except for DaemonSet or mirror pods). |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/ManagedClusterAutoScalerProfile",
"title": "ManagedClusterAutoScalerProfile",
"type": "object",
"description": "Parameters to be applied to the cluster-autoscaler.",
"properties": {
"balance-similar-node-groups": {
"type": "string",
"description": "Detects similar node pools and balances the number of nodes between them.",
"example": "example_value"
},
"daemonset-eviction-for-empty-nodes": {
"type": "boolean",
"description": "If set to true, all daemonset pods on empty nodes will be evicted before deletion of the node.",
"example": true
},
"daemonset-eviction-for-occupied-nodes": {
"type": "boolean",
"description": "If set to true, all daemonset pods on occupied nodes will be evicted before deletion of the node.",
"example": true
},
"expander": {
"type": "string",
"description": "The expander to use when scaling up.",
"enum": [
"least-waste",
"most-pods",
"priority",
"random"
],
"default": "random",
"example": "least-waste"
},
"max-empty-bulk-delete": {
"type": "string",
"description": "The maximum number of empty nodes that can be deleted at the same time.",
"default": "10",
"example": "example_value"
},
"max-graceful-termination-sec": {
"type": "string",
"description": "Maximum number of seconds the cluster autoscaler waits for pod termination when trying to scale down a node.",
"default": "600",
"example": "example_value"
},
"max-node-provision-time": {
"type": "string",
"description": "The maximum time the autoscaler waits for a node to be provisioned.",
"default": "15m",
"example": "example_value"
},
"max-total-unready-percentage": {
"type": "string",
"description": "Maximum percentage of unready nodes in the cluster. After this percentage is exceeded, the cluster autoscaler halts operations.",
"default": "45",
"example": "example_value"
},
"new-pod-scale-up-delay": {
"type": "string",
"description": "For scenarios like burst/batch scale where you do not want CA to act before the kubernetes scheduler could schedule all the pods.",
"default": "0s",
"example": "example_value"
},
"ok-total-unready-count": {
"type": "string",
"description": "Number of allowed unready nodes, irrespective of max-total-unready-percentage.",
"default": "3",
"example": "example_value"
},
"scan-interval": {
"type": "string",
"description": "How often the cluster is reevaluated for scale up or down.",
"default": "10s",
"example": "example_value"
},
"scale-down-delay-after-add": {
"type": "string",
"description": "How long after scale up that scale down evaluation resumes.",
"default": "10m",
"example": "example_value"
},
"scale-down-delay-after-delete": {
"type": "string",
"description": "How long after node deletion that scale down evaluation resumes.",
"default": "scan-interval",
"example": "example_value"
},
"scale-down-delay-after-failure": {
"type": "string",
"description": "How long after scale down failure that scale down evaluation resumes.",
"default": "3m",
"example": "example_value"
},
"scale-down-unneeded-time": {
"type": "string",
"description": "How long a node should be unneeded before it is eligible for scale down.",
"default": "10m",
"example": "example_value"
},
"scale-down-unready-time": {
"type": "string",
"description": "How long an unready node should be unneeded before it is eligible for scale down.",
"default": "20m",
"example": "example_value"
},
"scale-down-utilization-threshold": {
"type": "string",
"description": "Node utilization level, defined as sum of requested resources divided by capacity, below which a node can be considered for scale down.",
"default": "0.5",
"example": "example_value"
},
"skip-nodes-with-local-storage": {
"type": "string",
"description": "Whether the cluster autoscaler will skip deleting nodes with pods with local storage.",
"default": "true",
"example": "example_value"
},
"skip-nodes-with-system-pods": {
"type": "string",
"description": "Whether the cluster autoscaler will skip deleting nodes with pods from kube-system (except for DaemonSet or mirror pods).",
"default": "true",
"example": "example_value"
}
}
}